|
.net
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Simple code change deploy in 2.0In 1.1 if I made a simple code change I would just copy the dll in the bin
folder to the website and that's it. If I make a simple code change in 2.0 what file(s) would I need to copy to the web server? What about if I want to deploy the site "precompiled"? Thanks. Anyone? Bueller? Bueller? ;)
Show quoteHide quote "VB Programmer" <d***@emailme.com> wrote in message news:u2xMmTpEGHA.2036@TK2MSFTNGP14.phx.gbl... > In 1.1 if I made a simple code change I would just copy the dll in the bin > folder to the website and that's it. If I make a simple code change in > 2.0 what file(s) would I need to copy to the web server? What about if I > want to deploy the site "precompiled"? > > Thanks. > This is quite frustrating.
If I make 1 small code fix I shouldn't have to precompile/publish the ENTIRE site. In 1.1 I would just copy the dll over. How can I do it in 2.0? Please advise. (Especially annoying because for some reason it takes an ENORMOUS amount of time to publish my site to the server, even though the site only consists of 3 small ASPX pages. I had to even kill the process several times.) Thanks. Show quoteHide quote "VB Programmer" <d***@emailme.com> wrote in message news:eXNTulxEGHA.524@TK2MSFTNGP09.phx.gbl... > Anyone? Bueller? Bueller? ;) > "VB Programmer" <d***@emailme.com> wrote in message > news:u2xMmTpEGHA.2036@TK2MSFTNGP14.phx.gbl... >> In 1.1 if I made a simple code change I would just copy the dll in the >> bin folder to the website and that's it. If I make a simple code change >> in 2.0 what file(s) would I need to copy to the web server? What about >> if I want to deploy the site "precompiled"? >> >> Thanks. >> > > On Fri, 6 Jan 2006 22:11:06 -0500, "VB Programmer" <d***@emailme.com> In 2.0 you can use the web deployment project to wrap the site up intowrote: > >(Especially annoying because for some reason it takes an ENORMOUS amount of >time to publish my site to the server, even though the site only consists of >3 small ASPX pages. I had to even kill the process several times.) > a single .dll: http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx Thanks!!!!
Show quoteHide quote "Scott Allen" <scott@nospam.odetocode.com> wrote in message news:qjlvr19ri4fogctv0k0c8d53b29pg5ifs7@4ax.com... > On Fri, 6 Jan 2006 22:11:06 -0500, "VB Programmer" <d***@emailme.com> > wrote: > >> >>(Especially annoying because for some reason it takes an ENORMOUS amount >>of >>time to publish my site to the server, even though the site only consists >>of >>3 small ASPX pages. I had to even kill the process several times.) >> > > In 2.0 you can use the web deployment project to wrap the site up into > a single .dll: > http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx > > -- > Scott > http://www.OdeToCode.com/blogs/scott/
Other interesting topics
WebResource.axd request causing errors
when debugging long delay before hitting breakpoint in page load Don't show page in browser history 2.0 Custom Membership Provider! Calendar Control New to ASP.NET 2.0 asp.net 2.0 caching ASP.net 2.0 GridView edit mode problems GridView and XML problems ASP.NET process identity does not have read permissions to the global assembly cache |
|||||||||||||||||||||||