|
| Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free! |
Visual Studio 2005 vs VS.net 2003
|
Original Message
|
Name: Rashar
Date: November 23, 2005 at 13:49:44 Pacific
Subject: Visual Studio 2005 vs VS.net 2003OS: WIN XPCPU/Ram: 1.8 gig /512 DDR |
Comment: Hi, What are the differences between Visual Studio 2005 and Visual Studio.net 2003? Can I code vb.net in Visual Studio 2005 or is it just the generic VB coding? Is Visual Studio 2005 an upgrade to Visual Studio.net 2003? Thanks in advance.
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: SN
Date: November 23, 2005 at 14:22:55 Pacific
|
Reply: (edit)Visual Studio .Net 2003 uses version 1.1 of the framework, whereas 2005 uses version 2.0 of the framework. 2005 is an upgrade to 2003...Everything you can do in 2003 you can do in 2005. VB.Net is supported in 2005 - You won't see any 'generic' VB IDEs coming out from Microsoft. I've been using '05 since the day it came out on the 7th, and I really like it. It allows you to change code while debugging, so you don't have to restart the app to test your change. It also has better intellisense (the autocomplete stuff), better deployment features for windows forms applications (ClickOnce), and the languages in version 2.0 of the .NET framework have some serious improvements (generics). Good luck, -SN
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: Rashar
Date: November 23, 2005 at 19:22:31 Pacific
|
Reply: (edit)Thanks SN... I'm going to pick your brain again, or anyone else for that matter... Do you know what language the majority of those CRM applications are developed in, IE, Microsoft CRM, ACT, SalesForce Automation applications? Thanks in advance. Rashar
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: SN
Date: November 24, 2005 at 07:25:25 Pacific
|
Reply: (edit)The very large majority of applications (CRM or otherwise) sold on the shelf today are written in C++. -SN
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: InTRUdEr
Date: November 25, 2005 at 22:10:47 Pacific
|
Reply: (edit)Actually i dont recommend using VS .NET for creating shareware. Coz .NET applications can be decompiled from EXE back to full source without problems. There is such apps. I have tested. Unless you use some crypto tekst instead actual letters (strings) in procedures/function names.
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: SN
Date: November 26, 2005 at 07:48:12 Pacific
|
Reply: (edit)"Actually i dont recommend using VS .NET for creating shareware." I didn't know we were talking about shareware here... "Coz .NET applications can be decompiled from EXE back to full source without problems" Not full source...But pretty close. But there are plenty of applications out there that will obfuscate your code for you when you compile the app. VS.NET comes with the community edition of dotfuscator. If you use that tool and you don't anticipate very, very talented developers trying to hack your code, I doubt you'll have any problems even if your app ends up being wildly popular. But if you plan to deploy on a grand scale (ie thousands of installations), then you probably should not consider .NET because you might eventually want to make a version for Linux and Mac users. Good luck, -SN
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: Rashar
Date: November 27, 2005 at 06:17:02 Pacific
|
Reply: (edit)Actually, I plan to deploy the app on about 10 laptops. The sales managers who will be receiving this app has no clue about hacking / programming code, so I should be ok. But it is nice to know that the new vs.net comes with that tool. Thanks,
Report Offensive Follow Up For Removal
|

Post Locked
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Programming Forum Home
|
|
|