>Well, it's still time to create .Net. We had that before but it was too earlier. Now, this might be better. Especially that we have the same set of categories for those three forums, it would be ok to have only .Net framework forum.
>
>I would like however to request some feedback from whoever read this thread. Do you think that'd be the best to do?
>
>As for switching forum, you are probably not aware of it but working virtual eliminate that need. I never used the non virtual approach since it's been implemented. This is also the default since about a year now for all new members. Basically, there is no need to switch forum when you work in such a mode.
>
>As for what you say about your way of doing things in .Net, do you say that even if you focus on C#, that occasionnaly, you have to build several components in VB.Net and ASP.Net for example? And/Or, it's mostly a combination of both as to the way we should do things in the .Net framework?

That would be great, it gets my vote.

You are right in that I was not aware of a virtual -vs- non-virtual approach. Is this a feature available to everyone or only PUTM?

I have not found a situation that I had to build a class in a specific language. I have seen procedures that would be easier to write in say VB versus C# and vice-versa. This will become more obvious as more .NET languages become available. I do believe most developers will try to stick with a single language.

When I first started working with .NET I was writing and porting all code to C#.
As a seasoned (old fart) classic ASP developer I found myself converting numerous VBScript classes to C# and spending days to complete a single class. After I started the port of a encryption class I decided to try using VB.NET. The entire port took only minutes where a re-write would have taken days.

I think many ASP developers will find themselves in the same situation. Port to VB for ease, re-code later if warranted.