Microsoft Visual Studio 2008 Professional Edition-VISUAL STUDIO PRO 2008 WIN32 DVD DVD

...

of those other components. For us it is the language extensions in C# 3.0, for example, LINQ, and the more concise syntax to get lambda expressions to work that matters the most (the new "=>" operator). WCF (Windows Communications Foundation) is a new great programming framework that is used to build applications that inter-communicate. However, we will be using CCR instead for that purpose. The CCR primitives are very easy to use and great for multi-threaded applications with, for example, autonomous agents. As I understand CCR is scheduled to be included with Visual Studio 2010/2011 but you can start using the CCR library now with Visual Studio 2005/2008.

Visual Studio 2008 Professional is targeted towards Professionals (software engineers, small development companies, etc.). If you are a student or a hobbyist you should instead down load the four Express editions of the products which you get for free. However, for serious programmers they are not enough. I will put a link for the free downloads in a comment that I will add later. The four express editions are Visual Basic Express, Visual C++ Express, Visual C# Express, and Visual Web Developer Express.

It should be noted that the Express Editions have significantly reduced functionality. They only include a small set of tools, and libraries. There is no remote database support for data designer, no extensibility, no class designer and several other tools, no Microsoft SQL Server integration, no support for plug-ins. x64 compilers are not available for the Visual Studio Express edition and there is only a smaller express edition of MSDN. Missing C++ related items are, for example: C++ Name undecorator, Spy++, ATL trace, MASM, Visual C++ Web deployment tool, Server Explorer, no create GUID tool, CRT debug library, CRT source code, ATL, MFC, OpenMP, C++ Support library, etc. Naturally Visual C# and Visual Basic are also scaled down. The standard edition have somewhat reduced functionality and is targeted towards rich and serious students/hobbyists and poor professionals.

I currently have Visual Studio 6.0, Visual Studio 2003, Visual Studio 2005, and Visual Studio 2008 on my computer. I am using mostly Visual C++ and Visual C#, and on rare occasions Visual Web Developer. For that reason I believe that I can contribute some information regarding the difficulty related to upgrading.

It was not too difficult to convert Visual Studio 2005 C++/C# code to Visual Studio 2008 C++/C# code and the interface changes from Visual Studio 2005 and Visual Studio 2008 were minor simple improvements and added community components, which was nothing to cry about. When I went from Visual Studio 6.0 to Visual Studio 2003 and then to Visual Studio 2005, there were a lot of interface changes to get used to and some of my favorite tools were no longer available (class wizard), and the project file extensions were also different. Some of the projects I worked on also had problems with syntax errors that appeared only after the conversion.

When I converted a medium sized Visual C++ project (65,000 lines) from Visual Studio 2003 to Visual Studio 2005 I got more than 500 syntax errors due to changes in how scope was interpreted (from wrong to correct) and due to changes in what kind of declarations were allowed (from wrong to correct). We also had problems with run time errors that appeared only after conversion from Visual Studio 6.0 to Visual Studio 2003. The reason was that Visual Studio 6.0 executables often were able to execute bad code, like functions returning pointers to stack variables. The problem was really Visual Studio 6.0 not Visual Studio 2003/2005, but when you converted from Visual Studio 6.0 to Visual Studio 2003 the bad code caught up with you. Goofy project settings could also not be converted. It was a lot of work to clean this up.

When I converted the same medium sized Visual C++ project mentioned above from Visual 2005 C++ to Visual 2008 C++ I got no syntax errors and it ran fine the first time. When I converted a much larger application containing several projects with mostly C# code but also managed C++ code that loaded dynamic link libraries built using un-managed Visual 6.0 C++ code, it built and ran problem free instantly. The Visual Studio 2008 Conversion Wizard is also nice. However, there was a small gotcha. If you are doing the conversion offline (without source control management) and you answer yes, that you do want to have the project files made writable then this might actually not happen, with the result that the conversion fails. The failure to change the read-only status of the project files happened only for the projects containing both managed and un-managed C++ code (in a mostly Visual C# application). I don't know if that was a coincidence, or if I goofed.

So it seems like the conversion from Visual Studio 2005 to Visual Studio 2008 might be much less painful then conversions used to be. However, if you convert a Visual Studio 6.0 project to a Visual Studio 2008 project then you might have all the issues mentioned above as when converting to Visual Studio 2003 and Visual Studio 2005. However, this does not mean that Visual Studio 2005 and Visual Studio 2008 are similar. There are a lot of new and very useful components that have been added to Visual Studio 2008.

I already mentioned the language extensions in C# 3.0 (as compared to C# 2.0), for example, LINQ (querying data bases) which allows you to build strongly typed query expressions. Personally I am hoping that C# will in time more or less replace both C++ and Java. Another component I already mentioned is Windows Presentation Foundation (WPF); a new GUI toolkit that allows you to build extremely interactive and media-rich front ends (2D and 3D graphics and animations) for desktop applications (and web applications). The WPF Designer also provides a split view and snap lines for aligning controls and text. Windows Communication Foundation which allows you to build distributed applications (but we are using CCR instead). WWF allows you to define, execute and monitor workflows to model complex business processes, IntelliSense has been significantly improved and now supports JScript authoring and ASP.NET AJAX scripting. There is a Report Wizard, a class designer extension for unmanaged code, Object Browser improvements, and MSBuild recognizes when a system has multiple processors and uses all the available processors to reduce the build time.

I should add that I have bought two Visual Studio 2005 Professional from Amazon and I was happy with the price and the delivery. I did not get my Visual Studion 2008 from Amazon. As I am become more familiar with Visual Studio 2008 and gain additional experience with it I probably will edit this review and add information to it.

Microsoft Visual Studio 2008 Professional Edition-VISUAL STUDIO PRO 2008 WIN32 DVD DVD

...

components and Studio 2008 provides support and IDE. For us it is the language extensions in C# 3.0, for example, LINQ, and the more concise syntax to get lambda expressions to work that matters the most (the new "=>" operator). WCF (Windows Communications Foundation) is a new great programming framework that is used to build applications that inter-communicate. However, we are using CCR instead for that purpose. The CCR primitives are very easy to use and great for multi-threaded applications with, for example, autonomous agents. As I understand CCR is scheduled to be included with Visual Studio 2010/2011 but you can start using the CCR library now with Visual Studio 2005/2008.

Visual Studio 2008 Professional is targeted towards Professionals (software engineers, small development companies, etc.). If you are a student or a hobbyist you should instead down load the four Express editions of the products which you get for free. However, for serious programmers they are not enough. The four express editions are Visual Basic Express, Visual C++ Express, Visual C# Express, and Visual Web Developer Express. I will put a link for the free downloads in a comment that I will add later, and I will also give links for free .Net 3.5 download and CCR/DSS.

It should be noted that the Express Editions have significantly reduced functionality. They only include a small set of tools, and libraries. There is no remote database support for data designer, no extensibility, no class designer and several other tools, no Microsoft SQL Server integration, no support for plug-ins. x64 compilers are not available for the Visual Studio Express edition and there is only a smaller express edition of MSDN. Missing C++ related items are, for example: C++ Name undecorator, Spy++, ATL trace, MASM, Visual C++ Web deployment tool, Server Explorer, no create GUID tool, CRT debug library, CRT source code, ATL, MFC, OpenMP, C++ Support library, etc. Naturally Visual C# and Visual Basic are also scaled down. The standard edition have somewhat reduced functionality and is targeted towards rich and serious students/hobbyists and poor professionals.

I currently have Visual Studio 6.0, Visual Studio 2003, Visual Studio 2005, and Visual Studio 2008 on my computer. I am using mostly Visual C++ and Visual C#, and on rare occasions Visual Web Developer. For that reason I believe that I can contribute some information regarding the difficulty related to upgrading.

It was not too difficult to convert Visual Studio 2005 C++/C# code to Visual Studio 2008 C++/C# code and the interface changes from Visual Studio 2005 and Visual Studio 2008 were minor simple improvements and added community components, which was nothing to cry about. When I went from Visual Studio 6.0 to Visual Studio 2003 and then to Visual Studio 2005, there were a lot of interface changes to get used to and some of my favorite tools were no longer available (class wizard), and the project file extensions were also different. Some of the projects I worked on also had problems with syntax errors that appeared only after the conversion.

When I converted a medium sized Visual C++ project (65,000 lines) from Visual Studio 2003 to Visual Studio 2005 I got more than 500 syntax errors due to changes in variable (from wrong to correct) and due to changes in what kind of declarations was allowed (from wrong to correct). We also had problems with run time errors that appeared only after conversion from Visual Studio 6.0 to Visual Studio 2003. The reason was that Visual Studio 6.0 executables often were able to execute bad code, like functions returning pointers to stack variables. The problem was really Visual Studio 6.0 not Visual Studio 2003/2005, but when you converted from Visual Studio 6.0 to Visual Studio 2003 the bad code caught up with you. Goofy project settings could also not be converted. It was a lot of work to clean this up.

When I converted the same medium sized Visual C++ project mentioned above from Visual 2005 C++ to Visual 2008 C++ I got no syntax errors and it ran fine the first time. When I converted a much larger application containing several projects with mostly C# code but also managed C++ code that loaded dynamic link libraries built using un-managed Visual 6.0 C++ code, it built and ran problem free instantly. The Visual Studio 2008 Conversion Wizard is also nice. However, there was a small gotcha. If you are doing the conversion offline (without access to configuration control management) and you answer yes, to the question that you do want to have the project files made writable, then this might actually not happen, with the result that the conversion fails. The failure to change the read-only status of the project files happened only for the projects containing both managed and un-managed C++ code (in a mostly Visual C# application). I don't know if that was a coincidence, or if I goofed.

So it seems like the conversion from Visual Studio 2005 to Visual Studio 2008 is much less painful then previous conversions used to be. However, if you convert a Visual Studio 6.0 project to a Visual Studio 2008 project then you might have all the issues mentioned above as when converting to Visual Studio 2003 and Visual Studio 2005. However, this does not mean that Visual Studio 2005 and Visual Studio 2008 are similar. There are a lot of new and very useful components that have been added to Visual Studio 2008.

I already mentioned the language extensions in C# 3.0 (as compared to C# 2.0), for example, LINQ (querying data bases) which allows you to build strongly typed query expressions. Personally I am hoping that C# will in time more or less replace both C++ and Java. Another component I already mentioned is Windows Presentation Foundation (WPF); a new GUI toolkit that allows you to build extremely interactive and media-rich front ends (2D and 3D graphics and animations) for desktop applications (and web applications). The WPF Designer also provides a split view and snap lines for aligning controls and text. Windows Communication Foundation which allows you to build distributed applications (but we are using CCR instead). WWF allows you to define, execute and monitor workflows to model complex business processes, IntelliSense has been significantly improved and now supports JScript authoring and ASP.NET AJAX scripting. There is a Report Wizard, a class designer extension for unmanaged code, Object Browser improvements, and MSBuild recognizes when a system has multiple processors and uses all the available processors to reduce the build time.

I should add that I have bought two copies of Visual Studio 2005 Professional with MSDN from Amazon (actually my wife did) and I was happy with the price and the delivery. However, I did not get my Visual Studio 2008 from Amazon. As I am become more familiar with Visual Studio 2008 and gain additional experience from using I will probably edit or add to this review.

Special note: This review will soon receive 10-12 no votes from a few pranksters/detractors who no votes all reviews I submit without leaving a comment. I do not care, and it does not affect rank, which I do not care about either. The pranksters do not know anything about the product or the content of the review. Therefore>>> do not allow these no votes to mislead you into thinking that there is something wrong with the review.

Microsoft Visual Studio 2008 Professional Edition-VISUAL STUDIO PRO 2008 WIN32 DVD DVD

...

components and Studio 2008 provides support and IDE. For us it is the language extensions in C# 3.0, for example, LINQ, and the more concise syntax to get lambda expressions to work that matters the most (the new "=>" operator). WCF (Windows Communications Foundation) is a new great programming framework that is used to build applications that inter-communicate. However, we are using CCR instead for that purpose. The CCR primitives are very easy to use and great for multi-threaded applications with, for example, autonomous agents. As I understand CCR is scheduled to be included with Visual Studio 2010/2011 but you can start using the CCR library now with Visual Studio 2005/2008.



Visual Studio 2008 Professional is targeted towards Professionals (software engineers, small development companies, etc.). If you are a student or a hobbyist you should instead down load the four Express editions of the products which you get for free. However, for serious programmers they are not enough. The four express editions are Visual Basic Express, Visual C++ Express, Visual C# Express, and Visual Web Developer Express. I will put a link for the free downloads in a comment that I will add later, and I will also give links for free .Net 3.5 download and CCR/DSS.



It should be noted that the Express Editions have significantly reduced functionality. They only include a small set of tools, and libraries. There is no remote database support for data designer, no extensibility, no class designer and several other tools, no Microsoft SQL Server integration, no support for plug-ins. x64 compilers are not available for the Visual Studio Express edition and there is only a smaller express edition of MSDN. Missing C++ related items are, for example: C++ Name undecorator, Spy++, ATL trace, MASM, Visual C++ Web deployment tool, Server Explorer, no create GUID tool, CRT debug library, CRT source code, ATL, MFC, OpenMP, C++ Support library, etc. Naturally Visual C# and Visual Basic are also scaled down. The standard edition have somewhat reduced functionality and is targeted towards rich and serious students/hobbyists and poor professionals.



I currently have Visual Studio 6.0, Visual Studio 2003, Visual Studio 2005, and Visual Studio 2008 on my computer. I am using mostly Visual C++ and Visual C#, and on rare occasions Visual Web Developer. For that reason I believe that I can contribute some information regarding the difficulty related to upgrading.



It was not too difficult to convert Visual Studio 2005 C++/C# code to Visual Studio 2008 C++/C# code and the interface changes from Visual Studio 2005 and Visual Studio 2008 were minor simple improvements and added community components, which was nothing to cry about. When I went from Visual Studio 6.0 to Visual Studio 2003 and then to Visual Studio 2005, there were a lot of interface changes to get used to and some of my favorite tools were no longer available (class wizard), and the project file extensions were also different. Some of the projects I worked on also had problems with syntax errors that appeared only after the conversion.



When I converted a medium sized Visual C++ project (65,000 lines) from Visual Studio 2003 to Visual Studio 2005 I got more than 500 syntax errors due to changes in variable (from wrong to correct) and due to changes in what kind of declarations was allowed (from wrong to correct). We also had problems with run time errors that appeared only after conversion from Visual Studio 6.0 to Visual Studio 2003. The reason was that Visual Studio 6.0 executables often were able to execute bad code, like functions returning pointers to stack variables. The problem was really Visual Studio 6.0 not Visual Studio 2003/2005, but when you converted from Visual Studio 6.0 to Visual Studio 2003 the bad code caught up with you. Goofy project settings could also not be converted. It was a lot of work to clean this up.



When I converted the same medium sized Visual C++ project mentioned above from Visual 2005 C++ to Visual 2008 C++ I got no syntax errors and it ran fine the first time. When I converted a much larger application containing several projects with mostly C# code but also managed C++ code that loaded dynamic link libraries built using un-managed Visual 6.0 C++ code, it built and ran problem free instantly. The Visual Studio 2008 Conversion Wizard is also nice. However, there was a small gotcha. If you are doing the conversion offline (without access to configuration control management) and you answer yes, to the question that you do want to have the project files made writable, then this might actually not happen, with the result that the conversion fails. The failure to change the read-only status of the project files happened only for the projects containing both managed and un-managed C++ code (in a mostly Visual C# application). I don't know if that was a coincidence, or if I goofed.



So it seems like the conversion from Visual Studio 2005 to Visual Studio 2008 is much less painful then previous conversions used to be. However, if you convert a Visual Studio 6.0 project to a Visual Studio 2008 project then you might have all the issues mentioned above as when converting to Visual Studio 2003 and Visual Studio 2005. However, this does not mean that Visual Studio 2005 and Visual Studio 2008 are similar. There are a lot of new and very useful components that have been added to Visual Studio 2008.



I already mentioned the language extensions in C# 3.0 (as compared to C# 2.0), for example, LINQ (querying data bases) which allows you to build strongly typed query expressions. Personally I am hoping that C# will in time more or less replace both C++ and Java. Another component I already mentioned is Windows Presentation Foundation (WPF); a new GUI toolkit that allows you to build extremely interactive and media-rich front ends (2D and 3D graphics and animations) for desktop applications (and web applications). The WPF Designer also provides a split view and snap lines for aligning controls and text. Windows Communication Foundation which allows you to build distributed applications (but we are using CCR instead). WWF allows you to define, execute and monitor workflows to model complex business processes, IntelliSense has been significantly improved and now supports JScript authoring and ASP.NET AJAX scripting. There is a Report Wizard, a class designer extension for unmanaged code, Object Browser improvements, and MSBuild recognizes when a system has multiple processors and uses all the available processors to reduce the build time.



I should add that I have bought two copies of Visual Studio 2005 Professional with MSDN from Amazon (actually my wife did) and I was happy with the price and the delivery. However, I did not get my Visual Studio 2008 from Amazon. As I am become more familiar with Visual Studio 2008 and gain additional experience from using I will probably edit or add to this review.



Special note: This review will soon receive 10-12 no votes from a few pranksters/detractors who no votes all reviews I submit without leaving a comment. I do not care, and it does not affect rank, which I do not care about either. The pranksters do not know anything about the product or the content of the review. Therefore>>> do not allow these no votes to mislead you into thinking that there is something wrong with the review.

Microsoft Visual Studio 2008 Professional Edition-VISUAL STUDIO PRO 2008 WIN32 DVD DVD

...

components and Studio 2008 provides support and IDE. For us it is the language extensions in C# 3.0, for example, LINQ, and the more concise syntax to get lambda expressions to work that matters the most (the new "=>" operator). WCF (Windows Communications Foundation) is a new great programming framework that is used to build applications that inter-communicate. However, we are using CCR instead for that purpose. The CCR primitives are very easy to use and great for multi-threaded applications with, for example, autonomous agents. As I understand CCR is scheduled to be included with Visual Studio 2010/2011 but you can start using the CCR library now with Visual Studio 2005/2008.





Visual Studio 2008 Professional is targeted towards Professionals (software engineers, small development companies, etc.). If you are a student or a hobbyist you should instead down load the four Express editions of the products which you get for free. However, for serious programmers they are not enough. The four express editions are Visual Basic Express, Visual C++ Express, Visual C# Express, and Visual Web Developer Express. I will put a link for the free downloads in a comment that I will add later, and I will also give links for free .Net 3.5 download and CCR/DSS.





It should be noted that the Express Editions have significantly reduced functionality. They only include a small set of tools, and libraries. There is no remote database support for data designer, no extensibility, no class designer and several other tools, no Microsoft SQL Server integration, no support for plug-ins. x64 compilers are not available for the Visual Studio Express edition and there is only a smaller express edition of MSDN. Missing C++ related items are, for example: C++ Name undecorator, Spy++, ATL trace, MASM, Visual C++ Web deployment tool, Server Explorer, no create GUID tool, CRT debug library, CRT source code, ATL, MFC, OpenMP, C++ Support library, etc. Naturally Visual C# and Visual Basic are also scaled down. The standard edition have somewhat reduced functionality and is targeted towards rich and serious students/hobbyists and poor professionals.





I currently have Visual Studio 6.0, Visual Studio 2003, Visual Studio 2005, and Visual Studio 2008 on my computer. I am using mostly Visual C++ and Visual C#, and on rare occasions Visual Web Developer. For that reason I believe that I can contribute some information regarding the difficulty related to upgrading.





It was not too difficult to convert Visual Studio 2005 C++/C# code to Visual Studio 2008 C++/C# code and the interface changes from Visual Studio 2005 and Visual Studio 2008 were minor simple improvements and added community components, which was nothing to cry about. When I went from Visual Studio 6.0 to Visual Studio 2003 and then to Visual Studio 2005, there were a lot of interface changes to get used to and some of my favorite tools were no longer available (class wizard), and the project file extensions were also different. Some of the projects I worked on also had problems with syntax errors that appeared only after the conversion.





When I converted a medium sized Visual C++ project (65,000 lines) from Visual Studio 2003 to Visual Studio 2005 I got more than 500 syntax errors due to changes in variable (from wrong to correct) and due to changes in what kind of declarations was allowed (from wrong to correct). We also had problems with run time errors that appeared only after conversion from Visual Studio 6.0 to Visual Studio 2003. The reason was that Visual Studio 6.0 executables often were able to execute bad code, like functions returning pointers to stack variables. The problem was really Visual Studio 6.0 not Visual Studio 2003/2005, but when you converted from Visual Studio 6.0 to Visual Studio 2003 the bad code caught up with you. Goofy project settings could also not be converted. It was a lot of work to clean this up.





When I converted the same medium sized Visual C++ project mentioned above from Visual 2005 C++ to Visual 2008 C++ I got no syntax errors and it ran fine the first time. When I converted a much larger application containing several projects with mostly C# code but also managed C++ code that loaded dynamic link libraries built using un-managed Visual 6.0 C++ code, it built and ran problem free instantly. The Visual Studio 2008 Conversion Wizard is also nice. However, there was a small gotcha. If you are doing the conversion offline (without access to configuration control management) and you answer yes, to the question that you do want to have the project files made writable, then this might actually not happen, with the result that the conversion fails. The failure to change the read-only status of the project files happened only for the projects containing both managed and un-managed C++ code (in a mostly Visual C# application). I don't know if that was a coincidence, or if I goofed.





So it seems like the conversion from Visual Studio 2005 to Visual Studio 2008 is much less painful then previous conversions used to be. However, if you convert a Visual Studio 6.0 project to a Visual Studio 2008 project then you might have all the issues mentioned above as when converting to Visual Studio 2003 and Visual Studio 2005. However, this does not mean that Visual Studio 2005 and Visual Studio 2008 are similar. There are a lot of new and very useful components that have been added to Visual Studio 2008.





I already mentioned the language extensions in C# 3.0 (as compared to C# 2.0), for example, LINQ (querying data bases) which allows you to build strongly typed query expressions. Personally I am hoping that C# will in time more or less replace both C++ and Java. Another component I already mentioned is Windows Presentation Foundation (WPF); a new GUI toolkit that allows you to build extremely interactive and media-rich front ends (2D and 3D graphics and animations) for desktop applications (and web applications). The WPF Designer also provides a split view and snap lines for aligning controls and text. Windows Communication Foundation which allows you to build distributed applications (but we are using CCR instead). WWF allows you to define, execute and monitor workflows to model complex business processes, IntelliSense has been significantly improved and now supports JScript authoring and ASP.NET AJAX scripting. There is a Report Wizard, a class designer extension for unmanaged code, Object Browser improvements, and MSBuild recognizes when a system has multiple processors and uses all the available processors to reduce the build time.





I should add that I have bought two copies of Visual Studio 2005 Professional with MSDN from Amazon (actually my wife did) and I was happy with the price and the delivery. However, I did not get my Visual Studio 2008 from Amazon. As I am become more familiar with Visual Studio 2008 and gain additional experience from using I will probably edit or add to this review.





Special note: This review will soon receive 10-12 no votes from a few pranksters/detractors who no votes all reviews I submit without leaving a comment. I do not care, and it does not affect rank, which I do not care about either. The pranksters do not know anything about the product or the content of the review. Therefore>>> do not allow these no votes to mislead you into thinking that there is something wrong with the review.