No worries. I love it when a madcap scheme comes together On Fri, Jun 25, 2010 at 3:45 PM, Stephen Price <[email protected]>wrote:
> Update on this, moving the generated part of the project file into a target > file (its just a project file with naming convention of name.target) did the > trick. It now generates in one project, copies to the project that depends > on it and the IDE ignores the change (and the build server picks up the > change when that project is built). > > Thanks all (especially Michael) > > On Thu, Jun 24, 2010 at 2:15 PM, Michael Minutillo < > [email protected]> wrote: > >> Not sure if it works off the top of my head but you could put the T4 >> generated stuff in a separate project file and the import it into your >> static project file: >> http://msdn.microsoft.com/en-us/library/92x05xfs.aspx >> >> VS should only be watching the file it loaded and not the files it >> references so a regen shouldn't trigger a project reload. It's worth a shot. >> >> On Thu, Jun 24, 2010 at 2:12 PM, silky <[email protected]> wrote: >> >>> The other alternative is to put the relevant project in a different >>> solution, and don't open it, but reference it. I'm not sure if your >>> scheme supports this sort of change. >>> >>> My feelings would be like yours; rebuilding files you're working with >>> all the time is bad (I had this problem in dashy, which I solved by >>> generating the 'correct' file post-build, but this doesn't work for >>> you (as I understand you situation) because I wasn't generating >>> project files themselves, just configs). >>> >>> On 6/24/10, Stephen Price <[email protected]> wrote: >>> > I've had a look at what's being added to the project file, and its a >>> list of >>> > config strings from a global setting file. It contains various urls for >>> the >>> > target build. >>> > >>> > <#@ include file="globals.ttinclude" #> >>> > >>> > I'm assuming those string are then referenced in the project (I'm told >>> this >>> > project needs the include file to target particular publishing urls). >>> > >>> > I'll check out silky' suggestion to see if that helps. >>> > >>> > cheers, >>> > Stephen >>> > >>> > On Thu, Jun 24, 2010 at 1:49 PM, David Kean <[email protected] >>> >wrote: >>> > >>> >> Apart from unloading the project, I don’t believe you can do this. >>> >> >>> >> >>> >> >>> >> Why does the T4 build the project file? To add source files? If so, >>> can >>> >> you >>> >> make it take a filter, such as <Compiler Include="*.cs" />? >>> >> >>> >> >>> >> >>> >> *From:* [email protected] [mailto: >>> >> [email protected]] *On Behalf Of *Stephen Price >>> >> *Sent:* Wednesday, June 23, 2010 10:44 PM >>> >> *To:* ozDotNet >>> >> *Subject:* Generated project files >>> >> >>> >> >>> >> >>> >> Hi all, >>> >> >>> >> >>> >> >>> >> One of our project files is being generated from a tt file, and each >>> time >>> >> I >>> >> do a build the project file is replaced. This triggers the IDE to >>> reload >>> >> the >>> >> project file while its doing a build. >>> >> >>> >> Anyone know a way to have it automatically ignore or load the project >>> file >>> >> and not ask me? (just for this one project file). >>> >> >>> >> >>> >> >>> >> Please note this was not my idea, nor do I like it. It's caught me out >>> >> twice now, wondering why files I've added to the project suddenly are >>> not >>> >> in >>> >> the project when I build. Not to mention the reloading (see nag) of >>> the >>> >> project file during a build. >>> >> >>> >> >>> >> >>> >> Kind of hoping there's a property setting somewhere or maybe a build >>> >> order/dependency thing. >>> >> >>> >> >>> >> >>> >> cheers, >>> >> >>> >> Stephen >>> >> >>> >> >>> >> >>> >> >>> >> >>> > >>> >>> >>> -- >>> silky >>> >>> http://www.programmingbranch.com/ >>> >> >> >> >> -- >> Michael M. Minutillo >> Indiscriminate Information Sponge >> Blog: http://wolfbyte-net.blogspot.com >> > > -- Michael M. Minutillo Indiscriminate Information Sponge Blog: http://wolfbyte-net.blogspot.com
