post-build-event

问题 Is there a way to force the build to fail given certain conditions in the post-build event? The package I'm working with runs jslint and a few other solutions all together on post-build, I would like Visual Studio to fail if jslint produces an error. I am aware of the jslint plugin for VS2010 that will fail the build on error, but my requirements are restricting me to using the packaged bugchecking solution in which jslint is contained. 回答1: Post build events are basically batch scripts - you

问题 Is there any built-in macro to obtain the TFS Sourcecontrol Root directory in Visual Studio? For example just like $(ProjectDir), I would use $(TFSSourceControlRoot) or something like that? The reason I need this is to in order to use this path in the xcopy command which I will need as a part of a post build action. Instead of writing something like C:\Source\Scripts, I want to write something like $(TFSSourceControlRootDir)\Source\Scripts. 回答1: If you mean the root of the folder structure on

问题 My project needs to be packaged as a zip file for deployment. I want to create this zip file in a post build step. To achieve this I have installed a 7-Zip command line package via NuGet. This package provides an executable which I want to call in my post build step. I know that I could call it by providing the path to the installed package but this path contains the version number of the package so a direct reference will break when the package is updated. Is there some MSBuild variable that

问题 I have a bat file with code: echo Hello There > Result.txt @exit 0 File is located in folder named "batch" which is located in the project root. I am calling it with this code in post-build event: call "$(ProjectDir)batch\post.bat" I am using @exit 0 because otherwise I get error code 1 (which I guess tells me that command didn't succeed). When I double click on bat file or invoke it from cmd it creates a file. What do I need to do in order to make this work EDIT: Guys, make sure your file is

问题 I have a Qt-based application that uses a number of dlls that are built outside of the project. These dlls are checked into source because we will not be rebuilding them very frequently (they take on the order of hours to build, I don't want those to be in the main project). I want to copy those dlls into the appropriate directories (release, debug) once building has occurred. Is there a way to incorporate that copy step into the .pro file, so that the copying is propagated to each machine

问题 I am trying to do a poor man integration with xUnit.Net from inside Visual Studio as a post build event. What I want is when I press Shift+F6 (Build the test project), after a successful build it should run xUnit.Console.exe and output the result in an html file and afterward launch the html file inside the browser. Below is what I got so far and it work, but not to my liking (in that the browser will appear as a modal dialog of sort and I can't switch back and forward / toggle (using Alt-Tab

问题 I have a solution in Visual Studio in which I have a shared property sheet which contains a Post-Build Event command ( bar ) which needs to execute for every project. Foo.props > Common Properties > Build Events > Post-Build Event > Command Line = bar How do I then specify additional project-specific Post-Build Events? The usual "Inherit from parent or project defaults" is missing, and I would rather not have to manually add bar to every single project as it makes it hard to maintain. 回答1:

问题 I'm modifying the stack size of an assembly using editbin , see Increase stack size of main program or create a new thread with larger stack size for recursive code blocks? Now I'm asking myself: Is an assembly signed with a strong name before or after the post-build event? Because editbin is changing the assembly in the post-build event. My post build-event looks like that: "$(DevEnvDir)..\..\VC\bin\editbin.exe" /STACK:16777216 "$(TargetPath)" And my project .csproj file contains the

问题 Anybody know how to do this? I have a .bat script that I'd like to be able to use both from the command line as well as a post-build script in Visual Studio. The script takes arguments, some of which can contain spaces. The path to the .bat script can contain spaces, and is best expressed as a path relative to $(SolutionDir). I've tried what seems like a hundred variations of command lines with different enclosing quote and escape character combinations including: "$(SolutionDir)myScript.bat"

问题 I'm relatively new to Jenkins pipelines, but having implemented already a few, I've realised I need to start using jenkins shared library before I go mad. Have already figured out how to define some repetitive steps in the library and call them with less clutter from Jenkinsfile, but not sure if the same thing can be done for the entire post build section (thought I've read about to how to define the entire pipeline in the lib and similar), as this is pretty much static end of every single