1) I hand coded an ASPX/C# page in InterDev 6 yesterday, it worked fine<BR>2) I got excited and bought Visual C#.Net today<BR>3) Installed it but got no Intellisense on my aspx page<BR>4) Suddenly, The VS.NET inexplicably erased all the code in my aspx<BR>5) Went online to asp.net and learned that this (random deletion) is a known, unsolved issue<BR><BR>question:<BR>what is the preferred editor for ASP.NET?...why isn't there a Visual Interdev.Net? How can I get Intellisense for ASP.Net?<BR><BR>thanks<BR>-dtriny**** dude... that sucks man. Umm visual studio has intellesense like crazy-ness. I would say without a doubt that visual studio.net would be the editor of choice for coding asp.net. ( You say you bought visual c#.net Does that come with aspx support for creating webforms and webservices... sorry I dont know ). One thing I did notice about visual studio's intellesense was... if there was a bug in the page... intellesense stops working until you correct the syntax. It even nags you when it notices there is a syntax error. before you compile it!There is no stand-alone VI.Net because the functionality is now more or less built into C#/VB.Net/Visual Studio.Net.<BR><BR>I use VS...I've heard about that same random deletion error in VB. I know that MS is working on getting it resolved...<BR><BR>If you don't mind coding on the page, instead of using Code-Behind, MS has out the beta version of a free tool (Web Matrix) available on www.asp.net.<BR>It doens't intrinsically support code-behind, and there is no Intellisense, but the price is right, and it's a nice little tool.My personal take on it is that I won't learn and memorize the syntax for the controls and VB code if I leave it on.<BR><BR>So, I've resolved to buying a few books (up to 4 or 5 now, my personal favorites are ASP.NET Unleased and VB.NET Language In a Nutshell) and using my old ASP editors: Homesite and EditPlus.<BR><BR>I'm doing ASP.NET pages, code behind pages and working on a DLL now for my pages (all in VB.NET). All done by hand and manually compiling the DLL (thank God for batch files, typed it once and now just call the Batch file).<BR><BR>Just a personal preference, but I'm one happy camper.Yeah to hell with vs.net. Seriously. Its a huge program... like they make it so it basically wipes your ***. It makes it easy to add lots of code in a short period of time. And do things the long way in a short period of time. The long way which would be just really stupid to do if you were coding by hand... ( Typed dataset for every one of your asp.net pages in 5 minutes with stored proc ). But you dont really learn anything. I say learn how to code... learn how to use the compilers. Learn how to write one page of code that vs.net would make 5. Learn oop.
New user stress..
- Thread starter Gooxoplep
- Start date