 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / General / June 2007Deploying 2.0 WebSites
I'm still stuck on the .dll and bin folder mentality in 1.1. When deploying a 2.0 web application, there is no web .dll to deploy? So is this how we deploy in 2.0? 1. Copy the app_code folder 2. Copy the bin directory containing any pre-compiled dlls 3. Move BOTH aspx AND aspx.vb files into the applicable directories (is this correct?) If so, we're just duplicating the file system from the development machine to the production server? I guess this technically makes my life easier if I fix a particular bug in a single *.vb file. I can just copy the vb file over (rather than compiling and copying the entire web.dll over like in 1.1. Is this all correct? Or am I missing anything? Jason You are correct except #2. If you moving aspx files then you do not have precompiled DLLs unless you added some DLL as a reference. aspx and vb files compiled on a fly by asp.net. But if you wish you can precompile your application then you do not need to move aspx or vb files. George. > I'm still stuck on the .dll and bin folder mentality in 1.1. When > deploying a 2.0 web application, there is no web .dll to deploy? [quoted text clipped - 15 lines] > > Jason While I prefer the new methodology of web sites, there is the option to use a Web Application project rather than a Web Site project. The WAP follows a similar 2003 project set of complication and rollout rather than the direct copy/publish of .net 2.0. http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx has more information. -dl -- David R. Longnecker http://blog.tiredstudent.com G> You are correct except #2. If you moving aspx files then you do not G> have precompiled DLLs unless you added some DLL as a reference. G> G> aspx and vb files compiled on a fly by asp.net. But if you wish you G> can precompile your application then you do not need to move aspx or G> vb files. G> G> George. G> G> "daokfella" <jjbutera@hotmail.com> wrote in message G> news:1182800129.953097.181280@c77g2000hse.googlegroups.com... G> >> I'm still stuck on the .dll and bin folder mentality in 1.1. When >> deploying a 2.0 web application, there is no web .dll to deploy? [quoted text clipped - 14 lines] >> >> Jason Also, remember that VS 2005 SP1 includes WAP as the default without needing a separate install. With it, you get to choose the number and names of the dll's. Juan T. Llibre, asp.net MVP asp.net faq : http://asp.net.do/faq/ foros de asp.net, en español : http://asp.net.do/foros/ ====================================== > While I prefer the new methodology of web sites, there is the option to use a Web Application > project rather than a Web Site project. The WAP follows a similar 2003 project set of [quoted text clipped - 3 lines] > > -dl > G> You are correct except #2. If you moving aspx files then you do not > G> have precompiled DLLs unless you added some DLL as a reference. > G> G> aspx and vb files compiled on a fly by asp.net. But if you wish you > G> can precompile your application then you do not need to move aspx or vb files. > G> G> George. > G> "daokfella" <jjbutera@hotmail.com> wrote in message > G> news:1182800129.953097.181280@c77g2000hse.googlegroups.com... [quoted text clipped - 17 lines] >>> >>> Jason Ahh, good call; forgot about that. -dl -- David R. Longnecker http://blog.tiredstudent.com JL> Also, remember that VS 2005 SP1 includes WAP JL> as the default without needing a separate install. JL> With it, you get to choose the number and names of the dll's. JL> JL> Juan T. Llibre, asp.net MVP JL> asp.net faq : http://asp.net.do/faq/ JL> foros de asp.net, en español : http://asp.net.do/foros/ JL> ====================================== JL> "David R. Longnecker" <dlongnecker@community.nospam> wrote in JL> message JL> news:463c2475db38c98551dafbd18c@msnews.microsoft.com... >> While I prefer the new methodology of web sites, there is the option >> to use a Web Application project rather than a Web Site project. The [quoted text clipped - 34 lines] >>>> >>>> Jason > I'm still stuck on the .dll and bin folder mentality in 1.1. When > deploying a 2.0 web application, there is no web .dll to deploy? [quoted text clipped - 15 lines] > > Jason Right click on the name of your project at the top of your solution tree. Choose "Publish Web Site" The simple options box that follows will give you several options. I prefer to develop the app as a "file system" website. Then when I'm ready to deploy it, I run "Publish Web Site," uncheck "Make this web site updateable" (this forces stub pages for the aspx pages and rolls BOTH the aspx and code-behind pages into dll file(s),) and then publish to a local or intranet folder running IIS (i.e. 'C:\Inetpub \wwwroot'). Once it's in the IIS folder, I can test hit it with (http://localhost). Also, since everything is there, I can also copy it out to other servers easily, if that's what I need. That always seems to work very well. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.