| | |
Creating .EXE File
Please support our ASP.NET advertiser: Intel Parallel Studio Home
![]() |
•
•
Join Date: Jul 2005
Posts: 483
Reputation:
Solved Threads: 19
It makes sense just fine, she is just using the wrong word. She means dll. what you are looking for is in the bin subdirectory. All you need is to put the all non-codebehind pages(*.aspx, global.asax, etc) in the folder on the new server. You don't need the code behind pages(*.cs), but if in doubt, copy them all, they won't hurt anything being there. Then, create a subdirectory called bin and copy the contents of the bin (especially the dll,) directory from the development server to the new one.
Generic example:
You created the standar webapplication1 using VS and have just the standard webform1.aspx.
Copy webform1.aspx, web.config, global.asax into the virtual directory on the new server.
Copy the bin folder and paste it into the virtual directory on the new server.
Open IIS (start->run->inetmgr) on the new server
right click on the new virtual directory and hit properties.
In the application section hit the button that says create.
Then click on the documents tab and make sure your start page (default.aspx or whatever you called is listed in that box.
Hit ok and close out of IIS.
Voila, you are done
In the directory you will have the bin folder, the
Generic example:
You created the standar webapplication1 using VS and have just the standard webform1.aspx.
Copy webform1.aspx, web.config, global.asax into the virtual directory on the new server.
Copy the bin folder and paste it into the virtual directory on the new server.
Open IIS (start->run->inetmgr) on the new server
right click on the new virtual directory and hit properties.
In the application section hit the button that says create.
Then click on the documents tab and make sure your start page (default.aspx or whatever you called is listed in that box.
Hit ok and close out of IIS.
Voila, you are done
In the directory you will have the bin folder, the
•
•
Join Date: Dec 2004
Posts: 1,655
Reputation:
Solved Threads: 35
Not so. If you don't want to use the simple click-through wizard built-in to Visual Studio.NET, and would prefer to deploy your ASP.NET Applications through the command-line, then Microsoft recommends using the XCOPY method, as discussed here:
http://msdn2.microsoft.com/en-us/library/f735abw9.aspx
http://msdn2.microsoft.com/en-us/library/f735abw9.aspx
•
•
Join Date: Jul 2005
Posts: 483
Reputation:
Solved Threads: 19
hell it took me longer just to find the deployment wizard than it did to do it my way. As for the command line instructions, they do the same thing that I did. actually, I would probably just create a batch file with those command line instructions in it and use it whenever I wanted to put out updates
![]() |
Similar Threads
- Creating an exe file (C++)
- creating a .exe file of a web application (JSP)
- Creating a .EXE file (Java)
Other Threads in the ASP.NET Forum
- Previous Thread: error on search code
- Next Thread: creating pdf files
| Thread Tools | Search this Thread |
.net 2.0 3.5 ajax alltypeofvideos appliances asp asp.net beginner box browser businesslogiclayer button c# cac checkbox class commonfunctions compatible content contenttype countryselector courier dataaccesslayer database datagrid datagridview datalist deployment development dgv dialog dropdownlist dropdownmenu dynamic dynamically edit embeddingactivexcontrol fileuploader fill findcontrol flash flv formatdecimal formview gridview gudi iis javascript list listbox menu microsoft mouse mssql nameisnotdeclared news novell numerical opera order panelmasterpagebuttoncontrols problem radio ratings redirect registration relationaldatabases reportemail schoolproject search security serializesmo.table sessionvariables silverlight smoobjects software sql sql-server sqlserver2005 ssl tracking treeview unauthorized validatedate validation vb.net videos vista visual-studio visualstudio vs2008 web webapplications webarchitecture webdevelopment webprogramming webservice xsl youareanotmemberofthedebuggerusers






