How to create a web application project in the local IIS [SOLVED]
-
I'm using VS2010 and I can't figure out how to create a Web application project in the local IIS. I only seem to be able to do one of two things: 1. Create a Web Site project in the local IIS. I do this by choosing File>New>Web Site>ASP.NET Web Site with Web location set to File System. Then I click Browse and choose Local IIS. 2. Create a Web Application project in the local file system (not in the local IIS). I do this by choosing File>New>Project>ASP.NET Web Application. No option is provided to use the local IIS, only the local file system. It doesn't do any good to put the project in c:\inetpub\wwwroot\. I still wind up with a location like http://localhost:50758/[^]indicating that I'm using the Web server built into Visual Studio, not my local IIS. Hopefully there's some additional configuration option I must set in IIS to recognize the location of the project in localhost. Solution added Friday, July 16, 2010 2:25 PM PST: I had the solution to this problem in my back pocket all the time without realizing it. The first experimental ASP.NET project I ever started (to help me wade into the Wrox book, Professional ASP.NET 4 in C#) accomplished precisely what I was after, but I forgot what I did. After wading through responses I got in this thread (that did not provide the answer) I dug into my project settings and discovered the trick: Within Project>WebApplicationProject Properties on the Web tab, choose the Use Local IIS Web Server option. Then just Create Virtual Directory. Honestly, that's all there is to it. Oh, yes. You also originally create the project as described above in my #2 item, precisely the option that the Wrox book, Beginning ASP.NET 4 in C# on page 38 warns you against making the "mistake" of choosing because it "is not compatible with the exercises in this book." But I'll bet you I can figure out how to transfer what I learn from this book to a Web Application project that does run under the local IIS. So now I wind up with a location for my Website like http://localhost/PPT/Customers.aspx[^].
modified on Friday, July 16, 2010 5:43 PM
-
I'm using VS2010 and I can't figure out how to create a Web application project in the local IIS. I only seem to be able to do one of two things: 1. Create a Web Site project in the local IIS. I do this by choosing File>New>Web Site>ASP.NET Web Site with Web location set to File System. Then I click Browse and choose Local IIS. 2. Create a Web Application project in the local file system (not in the local IIS). I do this by choosing File>New>Project>ASP.NET Web Application. No option is provided to use the local IIS, only the local file system. It doesn't do any good to put the project in c:\inetpub\wwwroot\. I still wind up with a location like http://localhost:50758/[^]indicating that I'm using the Web server built into Visual Studio, not my local IIS. Hopefully there's some additional configuration option I must set in IIS to recognize the location of the project in localhost. Solution added Friday, July 16, 2010 2:25 PM PST: I had the solution to this problem in my back pocket all the time without realizing it. The first experimental ASP.NET project I ever started (to help me wade into the Wrox book, Professional ASP.NET 4 in C#) accomplished precisely what I was after, but I forgot what I did. After wading through responses I got in this thread (that did not provide the answer) I dug into my project settings and discovered the trick: Within Project>WebApplicationProject Properties on the Web tab, choose the Use Local IIS Web Server option. Then just Create Virtual Directory. Honestly, that's all there is to it. Oh, yes. You also originally create the project as described above in my #2 item, precisely the option that the Wrox book, Beginning ASP.NET 4 in C# on page 38 warns you against making the "mistake" of choosing because it "is not compatible with the exercises in this book." But I'll bet you I can figure out how to transfer what I learn from this book to a Web Application project that does run under the local IIS. So now I wind up with a location for my Website like http://localhost/PPT/Customers.aspx[^].
modified on Friday, July 16, 2010 5:43 PM
For method #1 have you selected http instead of File System?
I know the language. I've read a book. - _Madmatt
-
I'm using VS2010 and I can't figure out how to create a Web application project in the local IIS. I only seem to be able to do one of two things: 1. Create a Web Site project in the local IIS. I do this by choosing File>New>Web Site>ASP.NET Web Site with Web location set to File System. Then I click Browse and choose Local IIS. 2. Create a Web Application project in the local file system (not in the local IIS). I do this by choosing File>New>Project>ASP.NET Web Application. No option is provided to use the local IIS, only the local file system. It doesn't do any good to put the project in c:\inetpub\wwwroot\. I still wind up with a location like http://localhost:50758/[^]indicating that I'm using the Web server built into Visual Studio, not my local IIS. Hopefully there's some additional configuration option I must set in IIS to recognize the location of the project in localhost. Solution added Friday, July 16, 2010 2:25 PM PST: I had the solution to this problem in my back pocket all the time without realizing it. The first experimental ASP.NET project I ever started (to help me wade into the Wrox book, Professional ASP.NET 4 in C#) accomplished precisely what I was after, but I forgot what I did. After wading through responses I got in this thread (that did not provide the answer) I dug into my project settings and discovered the trick: Within Project>WebApplicationProject Properties on the Web tab, choose the Use Local IIS Web Server option. Then just Create Virtual Directory. Honestly, that's all there is to it. Oh, yes. You also originally create the project as described above in my #2 item, precisely the option that the Wrox book, Beginning ASP.NET 4 in C# on page 38 warns you against making the "mistake" of choosing because it "is not compatible with the exercises in this book." But I'll bet you I can figure out how to transfer what I learn from this book to a Web Application project that does run under the local IIS. So now I wind up with a location for my Website like http://localhost/PPT/Customers.aspx[^].
modified on Friday, July 16, 2010 5:43 PM
You can Create your Virtual Directory directly from IIS or from Visual Studio during creation of Web application. Here is my two article which will help you for both of these cases. 1.Beginner's Guide : Exploring IIS 6.0 With ASP.NET [^] 2. Deploying Web Sites Using Visual Studio 2005[^] Hope this will help you !
Cheers ! Abhijit Jana | MVP Web Site : abhijitjana.net | Follow Me @ twitter Read my Latest Article :Mastering Debugging in VS 2010
-
For method #1 have you selected http instead of File System?
I know the language. I've read a book. - _Madmatt
According to this Wrox book I have by Imar Spaanjaars (Beginning ASP.NET 4 in C#), p. 38, choosing HTTP enables you to open a remote site running IIS with the so-called Microsoft FrontPage Server Extensions, so that's not relevant. Also, I'm not interested in my option #1 because I want to create a Web Application project in my local IIS, not a Web Site project.
modified on Friday, July 16, 2010 11:56 AM
-
According to this Wrox book I have by Imar Spaanjaars (Beginning ASP.NET 4 in C#), p. 38, choosing HTTP enables you to open a remote site running IIS with the so-called Microsoft FrontPage Server Extensions, so that's not relevant. Also, I'm not interested in my option #1 because I want to create a Web Application project in my local IIS, not a Web Site project.
modified on Friday, July 16, 2010 11:56 AM
Books are not always correct or give you all of the information. Specify localhost rather than a remote location.
I know the language. I've read a book. - _Madmatt
-
Books are not always correct or give you all of the information. Specify localhost rather than a remote location.
I know the language. I've read a book. - _Madmatt
Mark Nischalke wrote:
Books are not always correct or give you all of the information.
Neither necessarily is any information you see in forums. I looked at MSDN documentation and what it says is that if the IIS is remote, it has to support Front Page Extensions. That's probably where Imar got his information, but it appears to be irrelevant to what he's telling his readers to do. Nowhere in his book does he entertain the notion that the reader might be interested in using the local IIS. Of course MSDN isn't always correct either. The only way you know what is stated in a book, forum, or MSDN is true or not is to try it out and see what happens. So I tried out what you suggest and I wound up with a Web Site (no project file), not a Web Application (which has a project file and delivers an assembly, not .cs files). So you're not answering my question. The other poster in this thread claims to be providing an answer for me, but it requires researching other posts he's made. When I get out from under what I'm currently doing (making my way through the second chapter of the Imar book), I'll look into his answer and hope he provides the answer I'm looking for. One of the "problems" with the Imar book is that 95% of the book (all but the last chapter) assumes you're using a Web Site (not a Web Application) and the Web server built into Visual Studio (not IIS), so for my needs it has two strikes against it, but it provides all the basics which I need to get straight in my head.
-
You can Create your Virtual Directory directly from IIS or from Visual Studio during creation of Web application. Here is my two article which will help you for both of these cases. 1.Beginner's Guide : Exploring IIS 6.0 With ASP.NET [^] 2. Deploying Web Sites Using Visual Studio 2005[^] Hope this will help you !
Cheers ! Abhijit Jana | MVP Web Site : abhijitjana.net | Follow Me @ twitter Read my Latest Article :Mastering Debugging in VS 2010
Abhijit Jana wrote:
Here is my two article which will help you for both of these cases.
I guess I didn't make it clear that I was only interested in the second case. I looked through both of your articles, looking for the answer to my problem, but I guess I couldn't see the forest for the trees. In the first place, both of your articles use old versions of IIS and VS that I am not running, so the old fashioned look of your screenshots sort of put me off. (Your articles really need updating.) In the second place, your second article was clearly addressing itself to Web Site projects, not Web Application projects and I thought I made it clear that I was only interested in Web Application projects. In the meantime I started looking through the configuration of the first ASP.NET project that I built for reading along in the Wrox book, Professional ASP.NET 4 in C#. Somehow I had managed to accomplish precisely what I was asking about in my original post in this thread, but for the life of me I couldn't remember what I did! It didn't help to review the early chapters of the above book, because that book is basically a reference that assumes you already know such basic material backwards and forwards and doesn't go into it. That's why I subsequently got the Wrox book, Beginning ASP.NET 4 in C# which fills in all the blanks for ASP.NET beginners, but which unfortunately explicitly states it won't help the reader get up to speed on Web Application projects. Well, all this mucking around did enable me to figure out how to accomplish what I originally asked: how to use the local IIS to host a Web Application project. I document that in my original post. So thanks anyhow, for prompting me to keep digging away for the answer, which I had in my back pocket all along without realizing it.