I'm working on a Silverlight 5 application, trying to use SlowCheetah to get my xml transformations to happen during the build process, so that it's only done during the deployment part of the build. My issue is that, although my "release" folder is getting the transformed file, when I release the code, the xap file isn't recognizing the transformed file and is bringing in the base *.ClientConfig file.
I've tried Len Charest's post without success.
Has anyone overcome this?
Related
I'm having an issue where I can run and use a compiled version of my project on my computer, but the moment i put the release onto another computer to run it pops up with a console for a split second saying it can't open System.Data.Common. I'm using .Net Version 4.7.2 and this is installed exactly the same on my other computer. I've even tried install VS on that one to compile the program from source code and it still doesn't work. I've checked the file it is getting the System.Data.Common.dll from and it is there and installed in the correct folder. I've tried removing it from the project through the project file and config file and I still get the same thing. It just seems to be the one dependency it is messing up for. I don't have a direct screen shot of the error since it is on another computer I was testing for but it just says that error and then says line 9 of login.cpp and that is just opening the form. Although System.Data is a necessary package for my project (since I need Data Tables), I do not use anything from System.Data.Common so if there is a way i can get it to not be considered on compilation other than the methods I've already tried, that will work too.
I have tried to remove the dependency from the vcxproj file and vcxproj.filters file. This did not work. I tried reinstalling .Net 4.7.2 on the computer I wanted to install it on. I've also tried removing the dependency from the exe.config file and none of these have worked. My last resort it to just straight up copy and paste all the code into a fresh project and keep going until I get the same error.
I have the following setup for my C++ application:
Project "Common" with 6 cpp source files. One of these cpp sources is named dataclasses.cpp. The output of this project is libgeneral.dylib, to be used in the next project below.
Project "Algorithm" with only one cpp source file. This project uses the libgeneral.dylib from above and outputs another dynamic library named libalgorithm.dylib, to be used in the project below.
Finally, project "CLI" has one cpp file source file and uses libalgorithm.dylib created above. It creates the executable cli.
(I created this structure because I plan on using parts of the code base in different applications in the future. In my mind, this structure keeps things modular and clean.)
I am able to compile/build everything and run the executable with a 0 return code. However, there is a computational error in the output triggered by running cli against certain data. I suspect the error is in dataclasses.cpp. So my plan was to open the file dataclasses.cpp in project CLI and mark a breakpoint at the right spot, and then run debug in CLI. But when I attempt that, the breakpoint appears as an empty white circle with a diagonal line and a message
The breakpoint will not currently be hit. No executable code is associated with this
line.
Yet this is not true, the line I have chosen is definitely an executable line.
Note that I am able to successfully use breakpoints in the one source file that is used in project CLI.
CLion version: 2022.2
MacOS 12.2.1
Question: How can I debug dataclasses.cpp while running in project CLI? I would prefer to not add any new files in project Common; I want to keep this as a tightly defined library. Note that before the data reaches the relevant part of dataclasses.cpp, it has gone through multiple manipulations in the code within projects Algorithm and CLI. I know that ideally I should write test cases for everything in dataclasses.cpp, but I would like to solve this known issue quickly first.
A similar question was raised here, Can I debug libraries (DLLs) directly using CLion?, and the answer suggesting creating an executable in the library project, which I'd like to avoid. Plus the post is six years old and I'm hoping things have changed.
I use an onsite build agent to perform my VSTS builds. This is working fine, sort of. I have 2 build definitions, one of which is a clone of the other and the only difference between the 2 is the solution that is built, all other parameters are exactly the same.
One of my builds completes without error and creates build artifacts and compiled code zip files in the 'build/1/a' artifacts folder. My other build completes without error BUT there are no build artifacts and compiled zip files created, my 'build/3/a' directory for this build is empty and I cannot see anywhere in the logs where the tasks to create this was executed, if at all. This did used to work before I cloned the build definition though. These are the MSBuild arguments that I have defined for both build definitions;
/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.artifactstagingdirectory)\\" /p:PackageTempRootDir="D:\Build\SiteManagerDev"
The only difference between them is the last parameter '/p:PackageTempRootDir'.
I have tried switching between the 2 directories for both build definitions to make sure it is not a permission error and the definition that finishes correctly works against either directory. I am starting to tear my hair out now and I have even tried creating a completely new build definition for the solution that creates an incomplete build and it is the same result, it is almost as if it is the solution itself that is causing the issue?
Any help would be greatly appreciated.
UPDATE: 05/02/2017
I think I finally understand what is going on! Question, if a build is manually triggered, not by a check-in trigger, if there have been no changes made to the code, and even though the build is executed, does this prevent the build artifacts from being created again because nothing has changed? The reason I ask is because I have found a strange in-house housekeeping routine that goes and deletes the contents of the 'D:\Build\1\a' directory on our build machine on a regular basis (I have no idea why!) and this results in there being nothing to publish UNTIL there is a code change checked in and then they are generated again! What a waste of everyone time this has been, my apologies and thank you for your help.
I'm working on a project which has a SQLite database, built by running "sqlite3 [db filename] < [schema filename]" from the Terminal on Mac OS X. I'd like to learn more about the projects system in Xcode, and ideally get it to run this Terminal command automatically when I build the project, additionally copying the created database into the output directory of the C++ project. I've been able to do similar things with Visual Studio before, and I get the impression from the options presented that I can do the same thing in Xcode.
I've added an external build target with the database schema files inside it (so they get source controlled too) and at first it was running with errors that too many arguments were being passed. However, I put single quotes around the arguments and now it runs. But I don't see any output. The file is not generated in the directory I set and I can't find it anywhere else. I was wondering if it took the single quotes as a single argument to sqlite3, but I can't find anything named that either.
I keep finding tutorials such as this one: http://b2cloud.com.au/how-to-guides/precompilation-run-script-in-xcode-4 but it appears that Xcode has changed since they were written and I'm having no luck on 5.0.1. I can't seem to get it to run shell scripts, (hopeful for a workaround) can't find the output of what appear to be successfully run commands, and cannot add Aggregate/External Build Tool projects to the dependencies of my code project, so even if I had it working, it would not rebuild the database with the source code.
I'm more after an outline of the best way to do this in 5.0.1, because I suspect my entire approach may be wrong here.
Thank you for your time.
I have been banging my head on a brick wall that seems to be easily worked around for everyone except me.
I want to setup css and js compression using a standard build on Team Foundation Server 2010. Below is what I've tried so far and failed. I am looking for a magic helping hand to guide me into setting this up the way professionals (SO is full of em) believe it should.
http://yuicompressor.codeplex.com/releases/view/46679 (dowload demo using post-build events)
This method looked promising as it did exactly as promised when you build your project in Visual Studio.
My msbuild Post-build command:
$(MSBuildBinPath)\msbuild.exe
"$(ProjectDir)MSBuild\MSBuildSettings.xml"
/p:CssOutputFile="$(TargetDir)..\Content\StylesSheetFinal.css"
/p:JavaScriptOutputFile="$(TargetDir)..\Scripts\JavaScriptFinal.js"
However when the build is run by TFS I get a lot of errors like these:
D:\Builds\3\CKB 2010_Build_CP\Sources\CKB
2010\My.Name.Space\MSBuild\MSBuildSettings.xml (61): Failed
to save the compressed text into the output file [D:\Builds\3\CKB
2010_Build_CP\Binaries..\Content\StylesSheetFinal.css]. Please check
the path/file name and make sure the file isn't magically locked,
read-only, etc..
So clearly the problem is the syntax in the Post-build command that is wrong. But I can't figure out how to make it work for both local and TSF builds.
Update 2011-08-17
As noted by Edward Thompson, I've tried adding a backslash to the path:
$(MSBuildBinPath)\msbuild.exe
"$(ProjectDir)MSBuild\MSBuildSettings.xml"
/p:CssOutputFile="$(TargetDir)\..\Content\styles.min.css"
/p:JavaScriptOutputFile="$(TargetDir)\..\Scripts\scripts.min.js"
And the result is this:
Failed to save the compressed text into the output file
[D:\Builds\3\CKB 2010_Build_CP\Binaries\\..\Content\styles.min.css].
Please check the path/file name and make sure the file isn't magically
locked, read-only, etc..
The problem is the difference in values with which TFS and Visual Studio run the msbuild command.
These are the steps I have taken to get proper YuiCompressor integration with Visual Studio 2010 and Team Foundation Server 2010.
In your desired project add a folder named 'MSBuild'
In this folder you should extract the files you download from the YuiCompressor project on CodePlex
Set the properties of these files like this:
Now open the MSBuildSettings.xml file and edit it according to the scripts and css files you want to have compressed. I have uploaded mine on pastebin since pasting it here caused problems with the editor.
Add the following postbuild event to your project. Note that the paths can differ for your environment.
IF "$(BuildingInsideVisualStudio)"=="" $(MSBuildBinPath)\msbuild.exe
"$(ProjectDir)MSBuild\MSBuildSettings.xml"
/p:CssOutputFile="$(TargetDir)_PublishedWebsites\$(ProjectName)\Content\styles.min.css"
/p:JavaScriptOutputFile="$(TargetDir)_PublishedWebsites\$(ProjectName)\Scripts\scripts.min.js"
IF "$(BuildingInsideVisualStudio)"=="true"
$(MSBuildBinPath)\msbuild.exe
"$(ProjectDir)MSBuild\MSBuildSettings.xml"
/p:CssOutputFile="$(TargetDir)..\Content\styles.min.css"
/p:JavaScriptOutputFile="$(TargetDir)..\Scripts\scripts.min.js"
Build the project and see if the files where created as expected.
Perform a check-in and watch the tfs build create the compressed files for you.
For debugging the tfs build, you'll find the logs in the msbuild log which is linked inside the normal tfsbuild log.
I hope this helps someone out there. I couldn't find a decent guide anywhere so now there is one here! If you have other suggestions, feel free to add them or post them in the comments.
One thing that sticks out at me is that you're using $(TargetDir)..\ - which expands to \Binaries..\. I suspect that you don't have a Binaries.. directory, and that this is supposed to be \$(TargetDir)\..\. (Ie, the parent of the Binaries directory.)