Menu
▾
▴
Re: [NAnt-users] how to publish or output to a directory with msbuildtask
|
From: spatemp s. <sp...@gm...> - 2008-09-07 19:32:58
|
Thank you all for replying. I went ahead and created web deployment project
for my Web site. This site use to be Web Site type of project and recently
I converted to Web Application type of project. When I did a build using
Web Deployment project, and deployed to Windows 2003 server, I am getting
following error when I try to access a page. It basically gives me CS0433
error.
Exception message:
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary
ASP.NETFiles\website\0638e07f\70302fea\App_Web_egeneral.master.7371103c.ladtpjhq.0.cs(112):
error CS0433: The type 'MasterPage_eMasterLanding' exists in both
'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary
ASP.NETFiles\website\0638e07f\70302fea\assembly\dl3\750696ff\006b49d8_2e10c901\masterpages.DLL'
and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary
ASP.NETFiles\website\0638e07f\70302fea\assembly\dl3\ef1b9231\002c67d1_1f10c901\WebSite.DLL'
Is this a build issue because when I do a build from visual studio 2008 and
xcopy the entire site to 2003 then it works fine, no errors. Also, it
works fine with my development box running windows xp. My site contains
folders like below with some .cs code in Old_App_Code folder. Once again
thank you all and any help in this regard would be greatly appreciated.
App_LocalResourcesApp_Themes
bin
Controls
CustomCalender
images
obj
Old_App_Code
Properties
RadControls
script
site
style
On Thu, Sep 4, 2008 at 3:48 PM, Bob Archer <Bob...@am...> wrote:
> See answers inline below.
> ------------------------------
>
> *From:* spatemp spatemp [mailto:sp...@gm...]
> *Sent:* Thursday, September 04, 2008 3:07 PM
> *To:* Bob Archer
> *Cc:* nan...@li...
> *Subject:* Re: [NAnt-users] how to publish or output to a directory with
> msbuildtask
>
>
>
> ok. So, by default Output path is set to bin\ folder and the solution is
> doing the build on say "Release" configuration. By setting output path to
> some folder other then say bin\, will it copy all .aspx etc.. for web
> application.
>
> *[Bob Archer] No, it will only copy the binaries (DLLs) to that folder.
> You would still need to copy the .aspx files yourself.*
>
>
>
>
>
> Basically I am looking for what publishing a site does from MSBUILD. I
> want to then take all that content and zip it up so that I can do a
> OnceClick deployment.
>
> *[Bob Archer] If you can do it from the command line in MSBUILD than you
> should be able to do it with nant calling msbuild. I have never used MSBUILD
> to do this though. See below on zipping it.*
>
>
>
> Also, what does web deployment project will give me and the benefits of
> using it with Web Application type of projects(not web site).
>
> *[Bob Archer] It will copy the .aspx files to a deployment location. It
> also lets you edit the web.config if say for example you want to change from
> a dev connection string to a staging/test connection string. See this blog
> post http://weblogs.asp.net/scottgu/archive/2005/11/06/429723.aspx . I
> have to admit I have never done this, I just use a nant task to copy the
> .aspx files to the deployment directory.*
>
>
>
> I can use xcopy but I want to avoid having to worry about excluding .cs
> file and the others that I dont want on my web server.
>
> *[Bob Archer] Probably easier to just include the files you do want. Here
> is the fileset I use though… (notice I exclude web.config because we deal
> with that another way.) *
>
> * *
>
> <copy todir="${outputPath}">
>
> <fileset basedir="${assemblyInfoPath}">
>
> <exclude name="**/obj/**"
> />
>
> <exclude name="**/My
> Project/**" />
>
> <exclude name="**/*.sln" />
>
> <exclude name="**/*.cs" />
>
> <exclude name="**/*.vb" />
>
> <exclude name="**/*.resx"
> />
>
> <exclude
> name="**/*.csproj*" />
>
> <exclude
> name="**/*.vbproj*" />
>
> <exclude
> name="**/*.resources" />
>
> <exclude name="**/*.plsk"
> />
>
> <exclude
> name="**/*.vsdisco" />
>
> <exclude name="web.config"
> />
>
> <include name="**" />
>
> </fileset>
>
> </copy>
>
>
>
> You could even use this file set right in a ZIP task so you don't need to
> copy somewhere and then zip after a copy.
>
>
>
> Hope this helps,
>
> BOb
>
>
>
>
>
> On Thu, Sep 4, 2008 at 10:09 AM, Bob Archer <Bob...@am...> wrote:
>
> I think the easiest way to do this is to set up a build configuration in
> your solution that specifies where you want the output to go to.
>
>
>
> Other than that you can just use the copy task after the msbuild task to
> move your files.
>
>
>
> You may also want to look at creating a web deployment project in your
> solution which I think MSBuild will run.
>
>
>
> As I said, several options here.
>
>
>
> BOb
>
>
>
>
> ------------------------------
>
> *From:* nan...@li... [mailto:
> nan...@li...] *On Behalf Of *spatemp spatemp
> *Sent:* Thursday, September 04, 2008 7:43 AM
> *To:* nan...@li...
> *Subject:* [NAnt-users] how to publish or output to a directory with
> msbuildtask
>
>
>
> I need to modify my nant scripts to publish or output web application to a
> directory. So, currently we have following in the nant scrpit:
>
>
>
> <
>
> msbuild project="${Solution.Filename}" >
>
> <
>
> property name="Configuration" value="${Solution.BuildConfiguration}" />
>
> <
>
> property name="Platform" value="Any CPU" />
>
> </
>
> msbuild>
>
>
>
> What I would like to do is create an output directory under each project
> and let MSBUILD task also publish or output it ot that directory. Then
> later on I can package that directory via zip and deploy it to various
> servers. It would be nice if it could have built in ${ProjectDir}\output or
> something like that.
>
> Any help would be appricated. Thanks.
>
> by the way I tried following inside msbuild and it seems to publish console
> projects etc.. but not Web Application type of project. It gives me some
> error about non publishable project or something.
>
> <
>
> arg value="/t:publish" />
>
>
>
>
>
>
>
|