About fluxmunki

fluxmunki · ‎Jan 20, 2010

Thanks for your reply. I've attached a detailed build log from the project I created to reproduce the problem. (With project output logging added). The interesting bit is: Project Output Files: EBSTestClient.Primary output:EBSTestClient.exe; EBSTestClient.Primary output:app.config; The desired name EBSTestClient.exe.config is present in the log, but I think this is more related to MSBuild building the project rather than the installer. I'll take a look at the installshield targets file a bit myself, see if I can figure out what's going on.

fluxmunki · ‎Jan 20, 2010

I'm using Visual Studio Team System 2008, (9.0.30729.1 SP) C# Projects Yeah that's the dialog I'm talking about (I think they renamed it a bit for 2008, but looks much the same). The dialog looks at all the projects in the solution and shows all the classes/methods etc, so I'd imagine the isproj is interrogated and as it's not a native project something throws a wobbly 🙂 Also "Unloading" the isproj from the solution makes it work (you don't have to fully remove it)

fluxmunki · ‎Jan 20, 2010

Sorry, but it's been a while since I posted, and no replies. I've recreated the problem with a really simple console app to check it wasn't anything to do with my project. Still happens!

fluxmunki · ‎Jan 20, 2010

Recently I noticed that the Visual Studio "Create Unit Tests" dialog (e.g. context menu when you click on a method) was broken. I've now narrowed it down to the presence of my Installshield 2010 installer (with Visual Studio Integration - isproj). If I remove the installshield project from the solution it works again. Looks like a bug to me!

fluxmunki · ‎Jan 09, 2010

I have an Installshield basic MSI project with project output from my executable which includes an app.config. When I build the installer in visual studio the installer includes the renamed file (Administrator.exe.config). However when I build with MSBuild the installer contains the file with it's original name (app.config). This is incorrect and stops the app working correctly. I've looked at the project outputs in the log file and it is picked up as being app.config. Any ideas what the problem could be or how I can get around it? I guess one answer would be to not include it as a "project output", but this seems a bit of a shame.

fluxmunki · ‎Jan 04, 2010

The output was being created for this project. I looked at the logged project outputs and noticed that the ones causing problems were all those that had been abreviated in the .isproj file. I tried changing these in the .isproj file to the full project name and it seems to have fixed the problem. Infragistics.CompositeUI.W changed to: Infragistics.CompositeUI.WinForms It is worth pointing out that this is just a workaround and really the isproj file should be created with project references that actually work with MSBuild. I'm sort of surprised that I've not seen other people with the same issue.

fluxmunki · ‎Dec 23, 2009

I have an InstallShield 2010 project with Visual Studio integration. The installer builds fine within VS IDE, but when I try to build it with MSBuild it fails with the following message: No outputs for project "Infragistics.CompositeUI.Winforms" were provided, but the installation project references "Infragistics.CompositeUI.Winforms.Primary output". This same message is repeated for several assemblies. I've seen some forum posts about this, but it looks like a slightly different issue, and it refers to old versions of Installshield so I assume this has been fixed. I've checked the project dependencies and build order in VS and the installer is dependent on them all and is build last. Any ideas?

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Re: MSBuild not renaming app.config

Re: Installshield Visual Studio Integration breaks "Create Unit Tests" dialog

Any ideas?

Installshield Visual Studio Integration breaks "Create Unit Tests" dialog

MSBuild not renaming app.config

Re: MSBuild No outputs for project [x] were provided, but the installation project...

MSBuild No outputs for project [x] were provided, but the installation project...