|
I have been using DOTNET extensively to make and test a .NET web application. However, I have NOT been using VisualStudio.NET to make it; at least not as much as I would like to. There are several reasons this is so and yes, they are nit-picky and simple, however they are still worth considering. In order to get code behind to work, at least the default way and the examples out there, I need to use the F5 key to run and debug. This is different from using the mk.bat file with the csc command line as I know there is only one file being made and where it's going to be. Not really so when I hit F5. Most all the support material out there, books you buy at Amazon, Borders and Barns and Noble, all are straight code examples that don't use VisualStudio.NET. (Even the examples in MSDN aren't that great with respect to their walkthroughs and are basically straight coding.) Why even bother to make a VS.NET Project or a VS.NET Solution when you know all your files are going to be in under one main sub-directory and the below directories anyway. Even an Enterprise Application, no matter how complex, should be designed simple enough to be done that way if possible. (for example look at the c:/winnt directory !!!) I like ASP.NET and the .NET _frame_work a lot as that allow me to use a code editor to make changes. I also know that Microsoft has done an incredible job of trying to make things simple in VS.NET. BUT, I would like at least a well written walkthrough and especially an FAQ that lets me know what is really going on and how I can make things AND DO things as simple a possible in VS.NET Even the IBuySpy applications confirms my feelings as they are no VisualStudio.NET Projects; just plain code which is more what web developers are used to anyway, even graphic web designers also. Can we just have an option just to show the Window Explorer files and folder in VisualStudio.NET????? If not, I know that when you make a project I can understand what's it's doing, however I still don't feel comfortable with VS.NET creating the Web Application in IIS as anyone who is actually hosting their site, like a corporate intranet, really want to do it themselves as they can see what is actually going on. 2 THINGS We made it easier to make a web page will still giving control by giving the Designer or Developer the ability to chose the Design View or the Code View. We are tying to make it easier to install a web application by just coping the files over, BUT that's not happening as anyway you look at it you have to interact with IIS and properly configure it. Perhaps, if there were a window what when you initially created a Web Project, (1) a Window would pop up that allowed you to chose to do everything in One Step OR (2) another Window what will walk you though each individual Step in creating the Web Application on IIS and tells you what is going on. (just like allowing anyone to view the code in a web page) * People need to know that if there is a Web Project out there on the Web they wish to learn from and download, that they need to use the same name when setting up IIS to open the project. If not, VS.NET should let them know about it, and what to do about it. Like, I can't open this project for you, however, this is what you need to do...blah blah blah.....Also I can do this for you, but what I need it this information...... This is how people learn, and considering the number of support and help sites on the Internet, Microsoft needs to really consider that, that is how all of us web developers learned HTML in the first place. I want to know what VS.NET is doing when making a project and importing a project off the Internet just like I want to know the code that works behind the web pages. So, honestly are you using VS.NET? Are you using some other Code Editor?
|
Favoured: 0
