build-process

问题 I've been trying to understand what Ant is used for but i still don't get it. Can someone give me one use case for which Ant is used for, something I can try to see why Ant is useful and what kind of things I can use it for? I do Java development in Eclipse and I'm just getting started with servlets and Google Web Toolkit. 回答1: Ant is a build tool. Say for example you have several projects in your Eclipse workspace, all of which are pieces of a larger application. To build it all into a jar

问题 We have a batch-based buildprocess and we are using MSBuild only for compiling our project-files from visual studio. We also have integrated wix into our build-process. To set the version of our software we specify in the main-build-script some environment variables, that we use during the build-process. My problem is, that i have to set the FileVersion of the Assembly (AssemblyFileVersion) in my assembly-informations. Is there a way to give the MSBuild-call a property with the version to set

问题 I am developing a VB.NET (4.5 framework) solution in Visual Studio 2015, Win10 OS, and have been able to run the builds uninhibited for several months, but now I am receiving the following error upon starting the build: vbc : error BC2012: can't open 'C:\MyProject\ProjR5\ProjR5\obj\Debug\ProjR5.exe' for writing: Access to the path 'C:\MyProj\ProjR5\ProjR5\obj\Debug\GenTagR5.exe' is denied. At first, VS2015 would give me the option to run the last successful build, but even that is no longer

问题 I have three different configurations on my project, all three do not require all files to be build into the application. Actually I'd prefer if I could exclude those files from the build, which would make my application a little more lightweight. What I'm looking for is #if MYCONFIG or #if DEBUG statement but for files. I've already read that this can be accomplished by manually editing the csproj file, but I can't find that anymore...and are there other ways? 回答1: There are two different

问题 Our workstations are running 64-bit Vista, and the production servers for our ASP.NET MVC web apps are 64-bit Server 2008 servers. However, our build server running TeamCity is a Server 2008 32-bit server. We will taking these builds and deploying them on the 64-bit production servers. The applications are written all in C#. Should I be concerned about doing the builds in a 32-bit environment? Is it necessary to upgrade our build server? 回答1: Technically, there should be no problem in doing

问题 When you are monitoring the TFS build from Visual Studio (2008 or 2005), you can see where it is up to. The issue is that I have some Post-Build custom steps I would like the developer to be able to see directly throught the UI. Those steps take some times and we can also get a "timing" of the build step. Any idea how to have it displayed? 回答1: This is the pattern that I normally use for adding steps to the build report in TFS 2008. (See http://code.msdn.microsoft.com/buildwallboard/ for the

问题 When you are monitoring the TFS build from Visual Studio (2008 or 2005), you can see where it is up to. The issue is that I have some Post-Build custom steps I would like the developer to be able to see directly throught the UI. Those steps take some times and we can also get a "timing" of the build step. Any idea how to have it displayed? 回答1: This is the pattern that I normally use for adding steps to the build report in TFS 2008. (See http://code.msdn.microsoft.com/buildwallboard/ for the

问题 There's not much more to add really than the above question. I have a fairly simple build process template, which has hardly deviated from the default one. I have two custom activities, which by recommendation live in a separate assembly within the same solution. However.... Opening the template takes about two minutes. Changing properties on an activity in the workflow, reordering activities in the workflow, adding activities to the workflow, all take between 30-60 seconds. It's completely

问题 I was going through a book that explain how to override 'default' lifecycle of Maven. It says: To define a new lifecycle for a packaging type, you'll need to configure a LifecycleMapping component in Plexus. In your plugin project, create a META-INF/plexus/components.xml under src/main/resources. In components.xml add the content as shown below, and you're done. With below configuration, I'm able to customize the default lifecycle for 'jar' packaging type. Now If I exeute $ mvn package It

问题 I was going through a book that explain how to override 'default' lifecycle of Maven. It says: To define a new lifecycle for a packaging type, you'll need to configure a LifecycleMapping component in Plexus. In your plugin project, create a META-INF/plexus/components.xml under src/main/resources. In components.xml add the content as shown below, and you're done. With below configuration, I'm able to customize the default lifecycle for 'jar' packaging type. Now If I exeute $ mvn package It