Publish MVC website using MSBuild and CruiseControl - msbuild

I am trying to publish a MVC2 Web app as part of our continuous integration using Cruise Control ccnet.config file with msbuild. I have searched through numerous posts but cant find the right answer or get the suggestions to work. Does anyone know how to get this going so I can output the published files to a directiory ont he build server?
I have this so far:-
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe C:\SVNWork\projectNAME_labelled\
projectNAME.csproj /noconsolelogger /p:Configuration=Release;outDir=Release\ /v:diag
ResolveReferences;_CopyWebApplication>
Can someone perhaps get in touch so I can ask them some questions?
Thanks Gregor

I have the a similar issue. The suggestions seem good although havent got it to successfully work.
Publish MVC v1 C# application through Cruise Control

Related

I cant find MVC 5 template on vs2017 community

please i have a issue; two issues as a matter of fact. I will upload screen shots to better explain my ordeal.
I am new to MVC and intend to start using MVC 5. the tutorial i have works with MVC5.
I have installed vs2017 community. When i star a new project, i find the "ASP.NET Web Application" template. which i select. after giving my project a name and selecting .NET framework version, the development frameworks that shows up for MVC, WEB FORMS, WEB API all have '4' on them (meaning version 4?). see attached screen shots
when i select MVC and my project folders are scafolded, in the App_start folder, i do not find the IdentityCOnfig.cs file (see attached screen shot)
can anyone please help me with how i can rectify this? i really do not know what is going on and need your help
thanks identityConfig.cs missing
MVC template showing '4'
Need choose User accounts I attached a Image

Work around for StoryQ report generation broken after introduction of Nunit3.0

First let me say the I tried in the StoryQ forum but there is no much activity there and I feel I wont get any answer there.
This is the issue, after introduction of Nunit 3.0 the StoryQ report generation is broken
After introduction on Nunit 3.0 the way to find where your application is running has changed, it used to be that:
Directory.GetCurrentDirectory()
was good enough, but now you are forced to use:
NUnit.Framework.TestContext.CurrentContext.TestDirectory
The thing about using GetCurrentDirectory is that now with Nunit 3.0 gives you something like C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\TESTWINDOW.
I suspect that StoryQ is using GetCurrentDirectory and is getting a UnauthorizedAccessException becuase is trying to create a folder in the windows folder mentioned above.
Is there a way I could force StoryQ to use the correct directory without me going into the code of StoryQ and change it?
I tried this and it seems to work:
Directory.SetCurrentDirectory(NUnit.Framework.TestContext.CurrentContext.TestDirectory);
Now StoryQ goes to the right directory to create his report.

MVC4 - AuthConfig.cs missing

I am trying to get started with the OpenAuth features of MVC4 as described here:
http://pluralsight.com/training/Player?author=scott-allen&name=mvc4-building-m7-security&mode=live&clip=9&course=mvc4-building
I already did start over again a couple of times in order not to miss anything, but even though I am choosing the right template (Internet Application) there is no AuthConfig.cs.
Nor do I find documentation what to do to get the required tasks done manually.
I am pretty sure this is a pretty dumb question, but maybe I don't find the answer because it is so obvious...
thx
I followed these steps:
Open File/New/Project
Select ASP.NET MVC 4 web Application
Then Select internet Application
Once the project was created there should be a AuthConfig.cs file within App_Start folder
unbelievable.. I used the RC Version of Visual Studio and even though I reinstalled MVC4 from scratch the recent version including the openauth extensions wasn't properly available.
Following the same steps on the regular Visual Studio Installation did the trick...

Need msbuild file that will publish a Web Application

Has anyone had success making an msbuild file that will publish a Web Application, not the old 2.0 web site but a Web Application?
This is not what I am looking for:
<MSBuild Projects="eRx.Web.SecureSiteShell.csproj" Properties="Configuration=Debug;OutDir=$(OutputFolder)\$(OutputWeb)\bin\;WebProjectOutputDir=$(OutputFolder)\$(OutputWeb)\" Targets="ResolveReferences;_CopyWebApplication" />
I tried simply using 'targets:Publish' but I get : Skipping unpublishable project.
Apparently this just isn't possible. My first hint was getting absolutely no response from this site.
I began to look into making a web setup project but was unsatisfied at having to edit the installation dialogues to get a custom installation folder. All I really need is something that will copy the published output of a Web Application (not Web Site you 2.0 peeps).
I think I have cheated the system by creating a simple Windows Setup program. Surprisingly I am able to include the primary output of my web application which satisfies my need. I DO have to manually add each projects debug symbols if I want them so the process can be lengthly but doable.
Like I said, not completely satisfied because I wanted to get the files in a nice deploy folder for my QA group to work with but feeding them an MSI has its advantages I suppose.
I leave this for anyone to comment on. I still can't believe I can't do this from msBuild or any other tool.

How to Step into NServiceBus 2.0 with Debugger and also Navigate in it with Resharper?

We've just newly decided to use NServiceBus on our project and we're experiencing some problems. Rather than "ask for a fish" every time we hit an issue, we'd prefer to "teach ourselves to fish". This means setting things up so we can step into the NServiceBus source code and understand NServiceBus more deeply.
We need some help figuring out how to pull this off. It is unclear how to get Visual Studio to successfully build NServiceBus upon each compile, since NServiceBus comes with its own Nant build process that uses ILMerge to create consolidated assemblies and so forth.
We have already tried building NServiceBus with the Nant script and then referencing those dlls and pdb's. However, that does not let us step everywhere, and it also does not let VS.NET and Resharper navigate via "Find Usages" and other features.
So what we would really like to create is a VS.NET Solution that builds our in-house software and NServiceBus, and allows us to seamlessly Step and Navigate between them.
Is this possible? What would we need to do to pull this off?
Not quite the exact answer you were looking for, but you can check out the post i made on debugging into NServiceBus which involves the following steps:
Downloading the source code.
Building the source code using the
"build.bat"
Then referencing the
dlls and pdb files in your
solutions, so that you can step into
the NServiceBus source code.
I've successfully change the logging behaviour to always to a Message.ToString() in our code so that the Log4Net logs were a bit clearer.
Check it out here:
http://www.craftyfella.com/2010/12/debugging-into-nservicebus-so-you-can.html
Hope it helps.
Dave