|
From: Jim G. <jg...@gm...> - 2005-06-10 14:20:08
|
Yeah, I realize that project exists... it's a nice project and I'm happy=20 that someone took on that challenge. The difference is that our addin will= =20 automatically run pre/post build events for each solution build.=20 On 6/10/05, ha...@ve... <ha...@ve...> wrote: >=20 > There's already a VS.NET <http://VS.NET> plugin on SourceForge : >=20 > http://nantrunner.sourceforge.net/ >=20 > features : >=20 > * adds a build tree node for each .nant or .build file found in your > open solution > * reads NAnt file imports adding all reachable targets to a tree > * puts targets with no description in the private sub-tree > * allows you to run targets with a single click > * redirects build output to the VS.Net <http://VS.Net> build output windo= w > * allows you add target specific properties > * allows you to filter targets with a simple show/hide methaphor > * allows you to kill a running build process >=20 > Hans >=20 > > I don't know if this would interest anyone, but we use a > > vs.net <http://vs.net><http://vs.net>addin, at work, that we can releas= e=20 > to the > > community. When we do a solution > > build, it'll search for a solution level build file. The addin runs all > > nant > > tasks before it hits the <solution> task. Then it uses > > vs.net <http://vs.net><http://vs.net>to build the solution normally...= =20 > after the > > projects build successfully in > > vs.net <http://vs.net> <http://vs.net>, nant is run again to execute al= l=20 > tasks after the > > <solution> task. Basically it allows us to run NAnt for all pre/post=20 > build > > tasks, while still allowing visual studio to build normally. > > > > > > > > On 6/10/05, Matthew Mastracci <ma...@ac...> wrote: > >> > >> >> We solved it in-house by creating a new solution configuration base= d > >> >> on the Release configuration and called it "NAnt". The NAnt > >> >> configuration disables all the projects and uses Makefiles to call > >> >> NAnt to build the debug configuration. > >> > > >> > This sounds very interesting. Please can you describe this more > >> detailed > >> ? > >> > What do you mean with "disable all projects" ? > >> > >> I don't have VS.NET <http://VS.NET> <http://VS.NET> in front of me, so= =20 > I'll try to > >> remember what we did. > >> Use the build configuration dialog to create a copy of your Release > >> configuration called "NAnt". Once you've created the copy, uncheck the > >> box that selects the projects to build. > >> > >> Use the C++ makefile project to create yourself a new, empty project. > >> For the build command of the project, specify: > >> > >> nant -f:your-nant-file -emacs your-build-target > >> > >> This will run the NAnt build whenever you try to build the Makefile > >> project. > >> > >> Once you've got your NAnt projects, disable the building of all=20 > projects > >> except your NAnt ones from your build configuration dialog. This way, > >> VS.NET <http://VS.NET> <http://VS.NET> won't attempt to build them=20 > under any > >> circumstances. > >> > >> In the end, this configuration should have Release selected for each o= f > >> your projects. > >> > >> We've been running with NAnt as our main build engine for some time no= w > >> (six months or more). I couldn't imagine going back to locked files. := ) > >> > >> >> Because VS.NET <http://VS.NET> <http://VS.NET> thinks you are=20 > building in release > >> mode, > >> it locks > >> >> release files and lets your debug build work perfectly. The only > >> >> problem with this solution is that VS.NET <http://VS.NET> < > http://VS.NET>'s default > >> intellisense > >> >> doesn't work properly in this mode. > >> >> > >> >> The solution for the intellisense problem is to shell out for a cop= y > >> >> of Resharper from Jetbrains. Their intellisense is source-code=20 > based, > >> >> rather than DLL-based like VS.NET <http://VS.NET> <http://VS.NET>.= =20 > :) > >> > > >> > I use ReSharper since they started theit EAP program and won't miss= =20 > it > >> any > >> > more ;-) > >> > >> Excellent - this means that you can work around VS.NET <http://VS.NET>= < > http://VS.NET>'s > >> autocomplete > >> problem. Note that if you did not have Resharper, you'd have to > >> occasionally compile in release mode to update your intellisense. > >> > >> Good luck, > >> Matt. > >> > >> > >> ------------------------------------------------------- > >> This SF.Net <http://SF.Net> <http://SF.Net> email is sponsored by: NEC= =20 > IT Guy Games. How > >> far can you shotput > >> a projector? How fast can you ride your desk chair down the office lug= e > >> track? > >> If you want to score the big prize, get to know the little guy. > >> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20 > >> _______________________________________________ > >> Nant-users mailing list > >> Nan...@li... > >> https://lists.sourceforge.net/lists/listinfo/nant-users > >> > > >=20 >=20 > |