I'm thinking of reworking this project to use the v2.0 of the .NET Framework and moving to C# for the base programming language.
The idea being that C# seems to be more common for developers, and it also gives a better compatability with other .NET CLR platforms (ie Mono, Portable .NET, Rotor, etc)
Before planning to do this I'd like to get a bit of feedback from you on wether this is something you want.
Please post any comments here.
- Richard.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have to say I'd second that. I've seen plenty of code online in C# that has no equivalent VB and those authors make no bones about it.
Besides, there are some very good VB -> c# converters out there (I've used the converse and they work reasonably well)
Maybe that might be worth a gander, if it were possible to change up the VB code just slightly so that a VB ->C# converter would run 100%, why not leave things in VB and just provide a c# conversion for those that want it.
That'd save time for doing other things that have real value.
Just my 2c
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2005-06-23
Hi Richard,
I'm using the framework in a C# project and we are also developing using other managed and unmanaged languages too.
I'm not a VB programmer, I've learned it by using the framework.
At first it was difficult to switch between C# and VB.NET, but after a while its easy.
Although it is desirable to maintain a project using only one development language, it becomes more and more common to
have two or more .NET languages and several unmanaged languages (C++, C, etc) in one project.
Personally, after I got used to developing the framework in VB.NET I'm not planning to switch to C#.
Just a though, having the framework support both languages may help in spreading the word about the framework.
Dan Mayer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think moving to v2.0 would be a great idea.
I'm already starting to move my current projects into VS2005, and not worrying about working on this in 1.1 would be a nice comfort.
Sooner of later it's going to need to happen, so why not do it now. It shouldn't be a bad transition, most of the code should work as is; with little modification.
Adam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm thinking of reworking this project to use the v2.0 of the .NET Framework and moving to C# for the base programming language.
The idea being that C# seems to be more common for developers, and it also gives a better compatability with other .NET CLR platforms (ie Mono, Portable .NET, Rotor, etc)
Before planning to do this I'd like to get a bit of feedback from you on wether this is something you want.
Please post any comments here.
- Richard.
Hi Richard,
Since I use VB, I personally don't have the need for the framework being in C#.
For me, having more in-depth documentation would be a higher priority.
Also, did you see my question about ASP.NET in request #1217277?
Thanks,
Wyatt
I have to say I'd second that. I've seen plenty of code online in C# that has no equivalent VB and those authors make no bones about it.
Besides, there are some very good VB -> c# converters out there (I've used the converse and they work reasonably well)
Maybe that might be worth a gander, if it were possible to change up the VB code just slightly so that a VB ->C# converter would run 100%, why not leave things in VB and just provide a c# conversion for those that want it.
That'd save time for doing other things that have real value.
Just my 2c
Hi Richard,
I'm using the framework in a C# project and we are also developing using other managed and unmanaged languages too.
I'm not a VB programmer, I've learned it by using the framework.
At first it was difficult to switch between C# and VB.NET, but after a while its easy.
Although it is desirable to maintain a project using only one development language, it becomes more and more common to
have two or more .NET languages and several unmanaged languages (C++, C, etc) in one project.
Personally, after I got used to developing the framework in VB.NET I'm not planning to switch to C#.
Just a though, having the framework support both languages may help in spreading the word about the framework.
Dan Mayer
So moving to C# is probably out.
Moving to .NET v2.0 is OK? Are people looking to get onto VS2005 sooner rather than later?
Hey Richard,
I think moving to v2.0 would be a great idea.
I'm already starting to move my current projects into VS2005, and not worrying about working on this in 1.1 would be a nice comfort.
Sooner of later it's going to need to happen, so why not do it now. It shouldn't be a bad transition, most of the code should work as is; with little modification.
Adam
Its official, Visual Studio 2005 has been released...
Haven't seen much activity around here lately...
Any word on moving the framework to 2.0?
Not yet - I haven't had too much time to spend on this lately.
I've just got VS2005 and I'm looking at some of the documentation on ADO at the moment to see where I can improve things.
- Richard
C# is prefered from this direction