Which Visual Studio .NET Version?
I've seen a copy of Visual Studio .NET Pro 2003 advertised for £185.
1. Is this out of date all ready as I've seen VS 2005?
2. Is VS 2005 for ASP.NET 2.0 or is another version coming out at some point?
3. Is it worth the money?
Suggestions welcome.
DJ
Re: Which Visual Studio .NET Version?
4. As I only ever use C# (for both Windows and Web Applications) is there any advantage in getting Visual Studio .NET over Visual C#?
DJ
Re: Which Visual Studio .NET Version?
VS 2005 isn't released yet.
Re: Which Visual Studio .NET Version?
That would make sense having 2005 in the name. It's being advertised to death on the Microsoft though which is why I wasn't sure if it was out yet!
In which case do you think it makes sense to wait for it to come out?
DJ
Re: Which Visual Studio .NET Version?
Yes, you should wait for it to come out. Some developers have started with 2005 already, but I hear there might be issues when you want to upgrade from the beta to the release version.
Re: Which Visual Studio .NET Version?
Yeah I think it seems to make sense to hold off for now.
Whats the difference between Visual Studio and Visual C# as a matter of interest?
Cheers
DJ
Re: Which Visual Studio .NET Version?
Quote:
Whats the difference between Visual Studio and Visual C# as a matter of interest?
Visual Studio is an IDE in which you can program in VB.NET, C# and a host of other languages.
C# is one of those languages.
Is that what you really wanted to ask?
Re: Which Visual Studio .NET Version?
No not at all! ;-)
Visual Studio .NET is a software IDE - so is Visual C#. Thing is apart from the fact that Visual C# only provides support for the C# lanaguage is there any other difference between the two. As I only use C# is there any point me buying Visual Studio .NET over Visual C#?
DJ
Re: Which Visual Studio .NET Version?
I see what you mean now.
I have no clue. :)
Re: Which Visual Studio .NET Version?
I don't think I've talked to anyone that does know. Everyone just pays the extra money and uses Visual Studio .NET. The thing is... I'm tight and I won't spend out the cash if I don't need it! ;) I just can't see the point of paying for stuff I won't use!
Anyone out there got a clue?
Cheers anyway mendhak.
DJ
Re: Which Visual Studio .NET Version?
Might I offer a suggestion...
Since VS 2005 probably won't be released until late August...
install the .Net sdk 1.1
http://www.microsoft.com/downloads/d...displaylang=en
And then pick one of these free ides...
For C# Windows Forms applications:
http://www.icsharpcode.net/OpenSource/SD/Download/
(pick the setup / no source code link)
For C# ASP.net applications
http://www.asp.net/webmatrix/default...dex=4&tabId=46
Or you can use IBM's Eclipse...
http://www.sys-con.com/webservices/article.cfm?id=360
At least this way you can get developing right now...
Re: Which Visual Studio .NET Version?
I been developing in .NET for some time now using Web Matrix I've just been thinking of upgrading to Visual Studio or Visual C# as it seems to be the industry standard.
DJ
Re: Which Visual Studio .NET Version?
In response to your earlier question, I believe the differences are that Visual C# is just that, but Visual Studio is all of the .NET languages and also comes with a few more tools.
Re: Which Visual Studio .NET Version?
Its the "few more tools" I'm worried about - am I gonna miss out on some cool stuff?!?
DJ
Re: Which Visual Studio .NET Version?
The .NET Obfuscator is the only one I remember off the top of my head. I'll double check when I'm at a Windows machine.
Re: Which Visual Studio .NET Version?
That would be cool - thanks!
.NET Obfuscator scambles dll's so they can't be decompiled right? - a useful tool hmmmm might not be able to save my cash.
DJ
Re: Which Visual Studio .NET Version?
Quote:
Originally Posted by dj4uk
That would be cool - thanks!
.NET Obfuscator scambles dll's so they can't be decompiled right? - a useful tool hmmmm might not be able to save my cash.
DJ
It scrambles the names of the methods and events and properties so that they're difficult to understand. They can still be accessed using System.Reflection.