Publish van website

[Guest]

Hello,

I have a website build with VS2013 based on the standard WebForms.
In the "old days" I used to Publish the website using the VS2013-Publish methode.
This generated a folder with the deployable items.
I used to copy this manualy to the ISS-connected folder to make it "live".

Now, I want to use the Buildmaster deployment.

I made it work so far, but saw a strange thing happening.

When I use the Publish action, the outputfolder did not get any "Class.cs" files in it.
These file are needed because ISS complaince about the lach of it.

Is there something I mis ?
Could you help me out ?

Kind regards
Martin

Product: BuildMaster
Version: 4.6.1

[Guest]

Ah, interesting -- most people work very hard to avoid having any .cs files in their output folder :)

Anyway, the reason the .cs files are not in the build output is because "Copy to Output Directory" is set to false.

By default, the Build .NET actions will discard things not in the output directory. The alternative approach is to do something like...

1. Get Latest to $ApplicationDirectory\Source
2. Build $ApplicationDirectory\Source\MyProject.sln
3. Capture Artifact from $ApplicationDirectory\Source

This approach will not utilize the automatic discarding of files not in the output directory.

[Guest]

Hi Alana,

Thanks for your quick response.
You're completly right related to the .cs file strategy.... :-)

I think it is related to my "standard" way I used to compile stuf in the past.
Backthen it worked fine for me, so uptill now (start using Buildmaster) there was no reason to investicate further possibilities.

The option "all files" in stead of "only files needed to run application" in the publishing was set to "all files".
Therefore of course all the .cs files where automaticaly included.

I did publish from VS2013 with the option "only...." and the outcome is now exacly the same as the outcome of the Buildmaster publish.
So far so good, you did put me on the right track and the difference is solved for me.

But now, (other discussion) I must tell IIS that this is a website with .dll in stead of the .cs files.
I know it is not a buildmaster issue, but could you perhaps direct me into the direction where to find this?

Thanks for your assistence,
Kind rgards
Martin

[Guest]

The Build MSBuild Project actions effectively just run msbuild.exe against your project files; so, I would start there. KB1052 offers some troubleshooting tips, see the "Issues with third-party tools and integrations" section for how to dig into the details.