eglhidlfjhkbe
New Member
I hate to post such a general and emotive type of question, but its bugging me big time!<BR><BR>I started tinkering with asp.net using UltraEdit (which i solely use for vanilla asp) but then decided later to go deeper into .net once i had a copy of vs.net beta. Now that I have vs.net i am irritated to the max with it and have been chopping and changing between using a text editor and vs.net. Things like validation are a breeze in vs.net however and then its easy to copy and paste until you are waxed with the syntax... I've also set up my ultra edit to compile .vb files etc just like when i use java...<BR><BR>So I hated Interdev for asp and now vs.net for asp.net - what are your guys opinions and is the learning curve that hectic in bypassing vs.net? And once again sorry for this post which has tendencies to become a flame war (!)<BR><BR>And btw, by vs.net i mean using it for asp.net and not for creating win32 apps etc...When I first started using VS.NET I was very irritated by it, but after fighting it and fighting it, I finally got to the point where I could use it to start building our customer extranet and product catalog. Now, once I get into more design-centric applications, I have a feeling it's going to wear out it's welcome, because it only seems to be able to do what it can do and isn't as flexible as I would need. Plus, I can't seem to turn off it's necessity to "correct" some things. The thing is still BETA/RC (I'm not using the RC1 yet, because it was not reccommended for Enterprise users, I may plug it in anyway), so I'm hoping things will improve, but I have a feeling I'm going to be heading back to DreamWeaver and Text Editors when more design (GUI) flexibility is required.I knew there was a reason I wasn't "upgrading" ...<BR><BR>from microsoft vs.net page<BR>"The Visual Studio .NET Release Candidate is recommended for users who have not installed Beta 2, or users previewing the .NET Compact Framework and Smart Device Extensions. Users of Visual Studio .NET Beta 2 may purchase and install the Release Candidate; however, the Release Candidate contains fewer features, and a "time bomb" will prevent usage after February 28, 2002. Beta 2 users will probably choose to wait for the release to MSDN of Visual Studio .NET, scheduled for late in the fourth quarter of 2001."It's also nasty that i can write something in a text editor, then open it in vs.net and it doesn't work - i first need to import namespaces and be a lot more specific like the passed parameters to a page_onload need to be System.Object whereas in 'plain text' mode all you need to pass is Object...<BR><BR>I think im going to stick to ultraedit and just dabble with vs.net when i need some intellisense help etc 
<BR><BR>Thanks for your input!<BR>Regards Anton
<BR><BR>Thanks for your input!<BR>Regards Anton