We are using msbuild command to restore nuget but package is not restoring with jenkins build.please find the following command.
please suggest solutions.also please suggest if any other way to achive it.Thanks in advance.
Initially i updated package documentformat.openxml to 2.11.1 and the build is success but when i update the same package to 2.11.3 if has thrown following exception.After that i tried updating some other package also but not updated and thrown same kind of exception as below.Please help.
Related
I am using conan io to create a package from pre build binaries. I found this post on the conan website: http://docs.conan.io/en/latest/creating_packages/existing_binaries.html but the problem is: Every time I try to use export-pkg command I get an error that this command is unknown. What is more I can neither create a --bare package. What is wrong?
Do you have any idea what commands to use?
Thank you in advance,
K.
So, it occured that I had a prehistoric version of conan. What was surprising because couple of minutes before I upgraded conan. What happened: the upgrade was not successfull (although eveyrthing looked fine) because I had installed pythonx86. As soon as I installed pythonx64 and re-upgraded conan I had access to these new commands,
just in case someone had similar issues....
I am working on a Patch sample using the following link. However, I am not able to uninstall the patch either from Control Panel or from the command line MSIEXEC /i "MsiPath" MSIPATCHREMOVE="PathToMSP"
Peter Marcu's Blog: WiX: Building a Patch using the new Patch Building System - Part 3
Can anyone please let me know how to successfully uninstall or rollback a patch?
Note: I have set the AllowRemoval attribute to "yes" in the Patch.wxs file for the Patch element.
I would turn off logging, because apparently it's unable to perform the logging. Or try an explicit log location on your uninstall command line. Also, it could be this:
https://support.microsoft.com/en-us/help/2564571/-error-opening-installation-log-file--verify-that-the-specified-locate
and a detour is suggested.
I am trying to get TeamCity up and running for a CI / CD server. So far I have it connected to my Git repo, it pulls the repo and builds. Great.
Now I am trying to publish it. (My web server is also the CI server and agent).
I keep getting this error:
C:\TeamCity\buildAgent\work\f56e1490ff15a5c4\P4P.Web\P4P.Web.csproj(1373, 5): warning MSB3026: Could not copy "\pagefile.sys" to "C:\inetpub\wwwroot\P4P\build\pagefile.sys". Beginning retry 8 in 1000ms. The process cannot access the file '\pagefile.sys' because it is being used by another process.
It ultimately fails and fails the entire publish process.
C:\TeamCity\buildAgent\work\f56e1490ff15a5c4\P4P.Web\P4P.Web.csproj(1373, 5): error MSB3027: Could not copy "\pagefile.sys" to "C:\inetpub\wwwroot\P4P\build\pagefile.sys". Exceeded retry count of 10. Failed.
C:\TeamCity\buildAgent\work\f56e1490ff15a5c4\P4P.Web\P4P.Web.csproj(1373, 5): error MSB3021: Unable to copy file "\pagefile.sys" to "C:\inetpub\wwwroot\P4P\build\pagefile.sys". The process cannot access the file '\pagefile.sys' because it is being used by another process.
I found this ow SO. I tried downgrading the Microsoft.CodeDom.Providers.DotNetCompilerPlatform and Microsoft.Net.Compilers packages to 1.0.0. I have even tried removing them entirely.
I have looked at all csproj files for references to these packages (including the package.config). Nothing.
I have no idea where to even begin to fix this.
My server is running Windows Server 2012 R2. I installed VS professional.
Any ideas?
I encountered the same issue.
The problem starts when you upgrade the DotNetCompilerPlatform to version 1.0.1.
To work around this issue you can downgrade to version 1.0.0 using the NuGet package manager.
EDIT: If you uninstall Microsoft.CodeDom.Providers.DotNetCompilerPlatform AND Microsoft.Net.Compilers, and then install the DotNetCompilerPlatform (has a dependency on the Microsoft.Net.Compilers package so it will automatically install that) package again the error disappears for good so it seems.
Also check this issue link - error MSB3027: Could not copy "C:\pagefile.sys" to "bin\roslyn\pagefile.sys". Exceeded retry count of 10. Failed
Anyone attempt using entity framework-beta8 migrations? Everytime I run the dnx ef command I get the following
"Error: . Please run dnu restore to generate a new lock file"
running dnu restore then gives the error
Could not find a part of the path "c:\users\Username\ .dnx\packages\Owin\1.0.0\Owin.1.0.0.nupkg.sha512
Any idea what's going wrong?
EDIT
Checking it now and the path on the C drive is 1.0 not 1.0.0..that seems to be part of the issue here. Not sure if it was the right thing to do but renaming the folders worked in the end
I tried #Lutando's suggestion but got a command prompt error
'dnx' is not recognized as an internal or external command, operable program or batch file.
If you get this, do the following:
dnvm upgrade
dnu restore
Then you should be back in business
So I pulled the source from https://svn.castleproject.org/svn/castle/DynamicProxy/trunk/
Open it up in vs.net 2008
problems:
vs.net can't open the assembly.cs
assembly signing failed
What am I doing, rather NOT doing?
Update
So I downloaded nant, setup the .bat file in my PATH so it works in cmd prompt.
I ran:
nant default.build
Getting this error:
build failed, \buildscripts\common-project.xml (48,3)
invalid element . Unknown task or datatype.
How exactly do I build the dynamicProxy project now?
update
This is what I did, see screenshot:
oh and my nant is:
#echo off
"E:\dev\tools\nant-bin\nant-0.86-nightly-2009-05-05\bin\Nant.exe" %*
http://img697.imageshack.us/img697/5623/castlebuildscreenshot.png http://img697.imageshack.us/img697/5623/castlebuildscreenshot.png
You can read the FM (how to build.txt). :)
You need to run the build script first using NAnt (http://nant.sf.net). This will generate the assembly.cs file. Take a look at the .build files in the tree to see what they are doing.
As for the assembly signing failing, check the project settings to get rid of references to CastleKey.snk. It should sign it using DynProxy.snk (in theory).
UPDATE:
The issue with NUnit is now fixed. Do a clean check out. I really have no idea why you're getting that error. Which version of NAnt are you using? Make sure you have the latest (earlier do not have support for .NET 3.5)
You should be able to just pull the source from the trunk, and build with nant (I just did that and it worked). Ok, I lied, looks like the reference to NUnit is wrong, so the unit test project will not build correctly:
BUILD FAILED - 0 non-fatal error(s), 1 warning(s)
D:\OLD\DynamicProxy\buildscripts\common-project.xml(295,5):
'nunit-console.exe' failed to start.
The system cannot find the file specified
Total time: 1.2 seconds.
BUILD FAILED
Nested build failed. Refer to build
log for exact reason.
Total time: 3.4 seconds.
However the important stuff (assemblyinfo generation) will succeed and you should be able to just open Castle.DynamicProxy2-vs2008.sln, fix the reference to the NUnit assembly hit F5 and build the code with no issues.
I just did it on a clean check out, and it worked.
Generally if you're planning to do modifications in DP codebase, it is advised to go to the Castle user group first, and discuss it there.