xGCC support
Hello MSBuild Users,
Just a reminder that we're always interested in suggestions for improving MSBuild.
For small suggestions, the best route is via opening a suggestion athttps://connect.microsoft.com/feedback/Search.aspx?SiteID=210. If there's a small change or improvement you'd like to see, that isn't really a bug, I'd encourage you to open a suggestion there: we can track it, and if it's possible, appropriate, and we have time, we'll address it.
For big suggestions ("please implement distributed build", "please add native code support") that's probably not a good way. Instead I'd suggest you let us know via this forum -- for example, by replying to this post. The team would like to know what's important to you and what you'd like to see in future versions: it'll help us prioritize what we do.
Dan
I have searched many forums, googled every mountain and investigated in order to fulfill them - as yet unsuccessfuly. I need therefore a GUI interface to allow me to build the TFSBuild.proj in a user friendly intuititive way
The following are my project requirements:
- Automatically build entire solution (did that)
- If successful, publish certain web app application projects and copy other project dlls and exe's to different directories
- If build failed, do nothing
I would be grateful If you can send me a simple .proj sample to do 2 & 3
Hi,
I don't know if this is considered a bug but there's that one little thing that i would really like:
Using the DependsOnTargets attribute makes your build quite hard to read so instead i was thinking of using the CallTarget task like this:
<target Name="t1">
<do Stuff here./>
<Calltarget Targets="t2"/>
</target>
<target Name="t2">
<do more stuff here/>
<CallTarget Target="t3"/>
</Target>
Very nice but the problem with this is if a task outputs some data and i put it in a new property, i loose its value in the next target...
So anyways, that's all i can see for now.
Thank you
A quicker way to edit the project files in visual studio and maybe a best practices write up for deploying windows services, and smart clients to different environments (development, staging, production)
Like I think this is a good idea to handle the getting the right settings in the app.config file for a windows app or windows service for three different environments but there might a better way of doing things? Well, I just started looking into msbuild today, so I am sure there is.
<Target Name="AfterBuild">
<Copy SourceFiles="$(SourceDir)production.config" DestinationFiles="$(TargetDir)$(AssemblyName).exe.config" Condition=" '$(Configuration)' == 'Release' " />
<Message Text="Copied the production configuration file $(SourceDir)production.config to $(TargetDir)$(AssemblyName).exe.config" Condition=" '$(Configuration)' == 'Release' " />
<Copy SourceFiles="$(SourceDir)staging.config" DestinationFiles="$(TargetDir)$(AssemblyName).exe.config" Condition=" '$(Configuration)' == 'Staging' " />
<Message Text="Copied the staging configuration file $(SourceDir)staging.config to $(TargetDir)$(AssemblyName).exe.config" Condition=" '$(Configuration)' == 'Staging' " />
<Copy SourceFiles="$(SourceDir)app.config" DestinationFiles="$(TargetDir)$(AssemblyName).exe.config" Condition=" '$(Configuration)' == 'Debug' " />
<Message Text="Copied the debug configuration file $(SourceDir)app.config to $(TargetDir)$(AssemblyName).exe.config" Condition=" '$(Configuration)' == 'Debug' " />
</Target>
I suggest making it easier to make suggestions. Make it as easy as replying to a thread.
You'll get less feedback when the developer is forced to go to a special web page which asks too many irrelevant questions. Don't make making suggestions so difficult.
I'm particularly interested in Visual Studio extensibility. Easily the number one issue with VS extensibility and MSBuild is the amount of time and effort required to grok them. A comprehensive book, wizards, helper apps, case studies are all needed.
The amount of knowledge and skill required to implement a language into Visual Studio is way too high. This isn't right guys.
My top concern/suggestion would be solutions.
Right now solution files are in a proprietary format that makes it extremely difficult to extend and build multiple solutions using MSBuild. I'd really like to see SLN files implemented as MSBuild files.
I'd like MSBUILD to support (at least) GCC cross-platform builds out-of-the-box, with appropriate project templates to choose from, and so on. Big hot thing, I know
I've actually implemented MSBuild Tasks for gcc, ld, ar and as myself. They implement only a subset of the gazillion options those tools can digest, but they did cover my project pretty well.
I'd like to share what I did with the community and possibly see the thing grow into a more complete solution for Visual Studio-based cross-platform development.
I'd attach the source to this post by don't see an option to do that.
Is anybody interested? How could we make this moving forward?
