|
-
Aug 15th, 2015, 02:03 PM
#1
Any difference between a valid C# class name and a valid VB.Net one?
I'm doing some CodeGen work and I want it to use either C# or VB.Net depending on the user selection.
One of the things that is needed is a valid class name - is there any need to implement two versions of this?
-
Aug 16th, 2015, 05:16 AM
#2
Re: Any difference between a valid C# class name and a valid VB.Net one?
I guess the only issue might be language keywords, which would be valid type names in one language but not the other, e.g. Integer or Date would be valid in C# but not in VB, or at least not unescaped.
-
Aug 16th, 2015, 03:06 PM
#3
Re: Any difference between a valid C# class name and a valid VB.Net one?
Spot on - as I discovered when code generation met the Turkish Lira currency code [TRY]... so it looks like I'm going to need to have two language specific functions.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|