Re: where did my dll go?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for responding,
What do you do about the images and other files that get deleted?

--
thanks (as always)
some day i''m gona pay this forum back for all the help i''m getting
kes


"Teemu Keiski" wrote:

Yup,

well, basically the one option without even doing the publish step
(essentially precompilation for deployment) is just xcopy everything on the
production server. It means deploying also the source code.

Personally, I prefer web deployment projects with the default model because
I get all the benefits of the new model (wdp doesn't change that, it isd
separate project is vs solution), but I also get the neatness of deployment
plus other things that WDPs bring (dll per folder, web.config settings
switch, control over what is deployed e.g MSBuild ) and so on.

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke

"WebBuilder451" <WebBuilder451@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D31074A9-79C9-4735-932D-21279B353DA4@xxxxxxxxxxxxxxxx
I perfer to use the builtin deployment, but this will delete the images
(and
other files) that exist on the wbsite. I don't mind copyingthe files
manuelly, but as you said the dlls are not (officially) created when you
hit
build site. So i've tried option 1 and this will work, but is not the way
they are recomending.
Thanks
kes
--
thanks (as always)
some day i''m gona pay this forum back for all the help i''m getting
kes


"Teemu Keiski" wrote:

And the model how you can actually get dlls is somewhat complicated (due
to
lots of options). By default with Publish Web Site command in VS2005
(essentially means precompiling for deployment where you also get
deployable
files) you get something, actually quite bunch of files to deploy to the
server

If you want to get to the model where you get single dll for building the
application, you have left two choices depending on the model how you
work.

1. if you want to work with the "web site" model, default in VS2005,
where
dll is not done when you build the web site project , you can download
Web
Deployment Project (WDP) add-on. It is basically seperate project to
VS2005,
to make deployable files (ddls) based on certain conditions you set
http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/

2) If you want to work with very similar model as you did in VS2003,
where
you were always required to have explicit compilation step (which
produced
one dll), but on the other hand certain compilation related semantics
were
very clear (which have changed with web site model), you can download Web
Application Project add-on
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/

I know, at first this seems very, very confusing, so you might want to
have
a look at these forum & blog posts to understand what the differences
really
are. There are no right or wrong answers right away, it is question of
how
you work, you get things done with both models, equally.

http://forums.asp.net/thread/1256579.aspx
http://webproject.scottgu.com
http://weblogs.asp.net/scottgu/archive/2006/04/05/442032.aspx

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke

"Mike Hildner" <mhildner.nospam@xxxxxxxxx> wrote in message
news:%23EQ$TENYGHA.1200@xxxxxxxxxxxxxxxxxxxxxxx
2.0 changed the way that works. Instead of putting the .dll in the bin
folder, things are located (default) at
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

Although if you're using any third party controls (like Infragistics),
you'll have an App_Licenses.dll in the bin folder.

Mike

"WebBuilder451" <WebBuilder451@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:06265E3F-3ACE-449A-A30E-F6AB51576B02@xxxxxxxxxxxxxxxx
I have a local serve that holds my source code and i'm using vs2005 for
2.0
to build the site. I'm runingthe site off my local pc (filesystem). I
built
the site but can't find the dll or the bin directory.
Any Ideas?


--
thanks (as always)
some day i''m gona pay this forum back for all the help i''m getting
kes








.

Relevant Pages

  • Re: where did my dll go?
    ... I perfer to use the builtin deployment, but this will delete the images (and ... By default with Publish Web Site command in VS2005 ... If you want to get to the model where you get single dll for building the ... a look at these forum & blog posts to understand what the differences really ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: where did my dll go?
    ... By default with Publish Web Site command in VS2005 ... If you want to get to the model where you get single dll for building the ... Deployment Project add-on. ... you'll have an App_Licenses.dll in the bin folder. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP.NET 2.0 deployment
    ... if you use web site mode, and precompiled mode you can deploy page single page change or just all dlls. ... if you use web application projects there will be an additional dll for the codebehind dll along with all the page dll's. ... I like the way that deployment of a new assembly is so simple, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: where did my dll go?
    ... They can be excluded from the deployment, as you can configure what the wdp ... Plus that since WDP actually creates just a dll, ... By default with Publish Web Site command in VS2005 ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Deploy VS2005 Web Site Project
    ... For ASP.NET 2.0 web site application project, it use a new develop & ... deployment, you're suggested to manually perform a precompilation on your ... "aspnet_compiler.exe" to do the precompilation. ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework)