.NET Benefit?
-
Hi, I'm trying to determine whether there would be any real benefit in migrating from VS6 to VS.NET. The projects I'm working develop desktop apps (not web apps) in C++. We currently employ MFC (for GUI clients) and ATL (for COM+ servers) frameworks and interface with SQL Server 2000 DBs. I can see the benefit if I was developing web based applications, but I'm not seeing it for the types of products that we build. Any thoughts? Thx/ Steve
-
Hi, I'm trying to determine whether there would be any real benefit in migrating from VS6 to VS.NET. The projects I'm working develop desktop apps (not web apps) in C++. We currently employ MFC (for GUI clients) and ATL (for COM+ servers) frameworks and interface with SQL Server 2000 DBs. I can see the benefit if I was developing web based applications, but I'm not seeing it for the types of products that we build. Any thoughts? Thx/ Steve
I don't see clearly the benefit. The .NET virtual machine is a totally $new environment$ to work with. Moreover, even upgrading to VC++.NET is questionable : if you do a lot of GUIs, you'll certainly miss the class wizard (it has been replaced with a far less powerful stuff). What VisualC++ .NET would bring you rather than features is the ability to work with both MFC/ATL and SQLServer all in the same tool.
How low can you go ?
(MS rant) -
Hi, I'm trying to determine whether there would be any real benefit in migrating from VS6 to VS.NET. The projects I'm working develop desktop apps (not web apps) in C++. We currently employ MFC (for GUI clients) and ATL (for COM+ servers) frameworks and interface with SQL Server 2000 DBs. I can see the benefit if I was developing web based applications, but I'm not seeing it for the types of products that we build. Any thoughts? Thx/ Steve
ATL/MFC have their own handfull of improvements in vs.net. ATL Server is a new addition. MFC/ATL share lots of classes. Also the compiler offers improved performance benefits. I guess its wise to compare the feature list and then asses the real benefits from them. Cheers Kannan :-)
-
I don't see clearly the benefit. The .NET virtual machine is a totally $new environment$ to work with. Moreover, even upgrading to VC++.NET is questionable : if you do a lot of GUIs, you'll certainly miss the class wizard (it has been replaced with a far less powerful stuff). What VisualC++ .NET would bring you rather than features is the ability to work with both MFC/ATL and SQLServer all in the same tool.
How low can you go ?
(MS rant)__Stephane Rodriguez__ wrote: if you do a lot of GUIs, you'll certainly miss the class wizard (it has been replaced with a far less powerful stuff). What's the bet that something like ClassWizard will re-appear? Actually I don't know whether any of those add-in gurus will provide the functionality if MS don't.:) Kevin
-
ATL/MFC have their own handfull of improvements in vs.net. ATL Server is a new addition. MFC/ATL share lots of classes. Also the compiler offers improved performance benefits. I guess its wise to compare the feature list and then asses the real benefits from them. Cheers Kannan :-)
I really appreciate all of the responses; this certainly helps out. Regarding the ATL changes, I was lead to believe that Microsoft's whole COM paradigm has gone away in .NET; i.e., .NET development projects would not be employing COM/COM+ technologies. Is this true? Thanks again for your insight, Steve
-
I really appreciate all of the responses; this certainly helps out. Regarding the ATL changes, I was lead to believe that Microsoft's whole COM paradigm has gone away in .NET; i.e., .NET development projects would not be employing COM/COM+ technologies. Is this true? Thanks again for your insight, Steve
Yes COM/COM+ is sent out of the door...no registry..no guids. But you can use the existing COM code by COM Interop in .net, but you incur a bit of performance penalty for that since all of your COM calls has to be marshalled.As for as COM+ is concerned .net has its own namespace something in the line of EnterpriseServices where you can do lot of stuff which you do in COM+ but not sure whether it contains all the stuff of COM+ or only a subset of them. HTH Cheers Kannan
-
Yes COM/COM+ is sent out of the door...no registry..no guids. But you can use the existing COM code by COM Interop in .net, but you incur a bit of performance penalty for that since all of your COM calls has to be marshalled.As for as COM+ is concerned .net has its own namespace something in the line of EnterpriseServices where you can do lot of stuff which you do in COM+ but not sure whether it contains all the stuff of COM+ or only a subset of them. HTH Cheers Kannan
As I understand it COM+ is still used under the hood. But I get the impression this is just transitional, i.e., until .NET covers all the functionality of COM+ natively (i.e., natively to .NET). Kevin
-
Hi, I'm trying to determine whether there would be any real benefit in migrating from VS6 to VS.NET. The projects I'm working develop desktop apps (not web apps) in C++. We currently employ MFC (for GUI clients) and ATL (for COM+ servers) frameworks and interface with SQL Server 2000 DBs. I can see the benefit if I was developing web based applications, but I'm not seeing it for the types of products that we build. Any thoughts? Thx/ Steve
If you generally distribute your apps over the internet, .NET is severly limiting your potential market due to the 22MB .net framework download. I agree that EVENTUALLY, everyone will have the framework installed, but untill then, would you download a 22.1MB application or a 100Kb application? Rick Eastes. http://www.eastes.net