By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,979 Members | 943 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,979 IT Pros & Developers. It's quick & easy.

VS2005 - Publishing Website - Best practice?

P: n/a
Hello

I'm asking myself what the best practice is, when publishing a asp.net 2.0
website. So when I precompile the website, to put it online, i get a lot of
DLLs and ascx/aspx files. So i put them online, and all works, so far, so
good.

But the question is now, when I make a simple change in a .cs-File, then I
publish again the website, to get all precompiled dlls, so I have to upload
again all DLLs, ok, that's ok, but I also have to upload all ascx and aspx
files, because the reference has changed.

Has someone a solution to this??

Thanks
Patrick
Jan 17 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Unless you're adding functions or methods leveraged in your aspx/ascx
files, you shouldn't have to upload them as well.
--
Garth H
we*******@spamcop.net
Microsoft Certified Professional
Macromedia Certified Developer
Jan 17 '06 #2

P: n/a
yes, that was like this in Visual Studio 2003. But in the 2005 when
publishing the website, to the *.aspx/ascx something like this is added:

<%@ page language="C#" autoeventwireup="true" inherits="Admin,
App_Web_d5-k97r2" %>

and as you can see, inherits sais "class", "DLL", in this case the DLL-Name
is "App_Web_d5-k97r2.dll", but when publishing again the solution, this name
changes, and then dhte aspx referers to a wrong old dll.


"Garth H" <we*******@spamcop.net> schrieb im Newsbeitrag
news:43**************@spamcop.net...
Unless you're adding functions or methods leveraged in your aspx/ascx
files, you shouldn't have to upload them as well.
--
Garth H
we*******@spamcop.net
Microsoft Certified Professional
Macromedia Certified Developer

Jan 18 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.