I'm trying to set up CruiseControl.Net using SourceSafe as our source code repository. Looking at the example code in the CC.Net documentation I need to provide a path to the SourceSafe executable in the config file:
<sourcecontrol type="vss">
<executable>C:\Program Files\Microsoft Visual Studio\VSS\win32\SS.EXE</executable>
<project>$/CCNET</project>
<username>buildguy</username>
<password>buildguypw</password>
<ssdir>c:\repos\</ssdir>
<applyLabel>false</applyLabel>
<autoGetSource>true</autoGetSource>
<alwaysGetLatest>false</alwaysGetLatest>
<workingDirectory>c:\myBuild</workingDirectory>
<culture>fr-FR</culture>
<cleanCopy>false</cleanCopy>
<timeout units="minutes">10</timeout>
</sourcecontrol>
Sadly, we're running SourceSafe through Citrix so I don't have direct access to the SourceSafe executable. Any ideas how to get around this? Is it even possible?
No, you can't get this to work without direct access to the exe.
Related
I want VS let me use remote debbuging on Linux machine. I have downloaded necccessary packages and tools for this goal, so, I've denoted output and build directories. Build directory is created always successfully, but next step is Makefile that is not run, because CMakeList.txt is not sent from Windows machine.
I text in Additional Sources To Copy that this file should be copied, but I cannot know a reason of unsuccessful action. Only make command notifies me that this file does not exist. I guess this problem is in Visual Studio!
I have solved the problem and totally sure, that these things will exactly help you out!
https://developercommunity.visualstudio.com/content/problem/447310/2019-makefile-project-doesnt-copy-source-on-build.html
Fix the file
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Application Type\Linux\1.0\Linux.Makefile.targets
243 line, add this:
<Target Name="PrepareForNMakeBuild" DependsOnTargets="SetBuildDefaultEnvironmentVariables;SetUserMacroEnvironmentVariables;_RequiresRemoteConnection;_CopySources;">
Never use '~' when you denote pathes on remote machine in properties of debbuging, only like
/home/machine_name/project_name/$(SolutionName)/$(USERNAME)
I am looking for the path of Oracle.DataAccess.dll file on a linux server.
Usual location of the file is:
"/Database/oracle/product/11.2.0/dbhome_1/ODP.NET/bin/2.x"
But there is no directory named ODP.NET in the location "/Database/oracle/product/11.2.0/dbhome_1/"
I also tried searching for the directory using the following command.
find / -name "ODP.NET"
Anyone has solution for this problem?
DDLs are libraries for windows. Those libraries do not work on Linux.
AFAIK, ODP.NET means "Oracle Data Provider" for .NET, whichis a Microsoft framework and probably does not work with Linux
I'm trying to compile Python 2.7 with clang on Windows. I thought a solution to doing this would be to specify the properties CLToolPath and CLToolExe. However, when I set these properties in the project files, msbuild seems to just ignore them and continue using the Microsoft compiler.
The weird thing is that when I specify those properties on the command line, msbuild does actually pick them up. (But due to other aspects of the way Python 2.7 is set up, the build doesn't actually succeed that way, so it doesn't solve the problem. It just proves these are the right properties.)
This is the relevant section of a project file
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<Link>
<SubSystem>Console</SubSystem>
</Link>
<ClCompile>
<CLToolPath>C:\llvm\build\Release\bin</CLToolPath>
<CLToolExe>clang-cl.exe</CLToolExe>
</ClCompile>
</ItemDefinitionGroup>
And this is the command line I'm using
msbuild /t:clean,build /p:Configuration=Release /p:TrackFileAccess=false /p:Platform="x64" /fileLogger pcbuild.sln
Any idea what could be causing the properties to be ignored?
You're putting it to a wrong place. Find relevant PropertyGroup tag and add <CLToolExe> and <CLToolExe> to it as follows:
<PropertyGroup>
<CLToolExe>clang-cl.exe</CLToolExe>
<CLToolPath>C:\llvm\build\Release\bin</CLToolPath>
</PropertyGroup>
I have added some variable to PATH, such as
set resultPath=C:\Temp\Results
set platform=x64
And I want to use this variable in microsoft test configuration file .runsettings. e.g.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<RunConfiguration>
<ResultsDirectory>$(resultPath)</ResultsDirectory>
<TargetPlatform>$(platform)</TargetPlatform>
</RunConfiguration>
</RunSettings>
I tried both mstest.exes and vstest.console.exe by using configuration .runsettings file as above, but failed. The .trx file was created under .\$(resultpath) folder and one of test cases failed because it need x64 environment binaries to run, the default platform of microsoft test is win32.
Any comment?
My OS is win7, Visual studio 2012.
This isn't currently supported but you can vote for it at https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/7491553-unit-test-configuration-file-runsettings-support
I've installed the IIS Express 7.5 Beta 3 and tried it on multiple computers (Windows 7, Windows Server 2008 R2 and Windows XP) and on each one of them I get the following error when running
iisexpress /path:e:\onlineinvoices\
This is the error. It seems it can't find the applicationhost.config file. I've searched for this file myself too and found it in the AppServer folder of IISExpress installation folder.
Copied template config file 'C:\Program Files (x86)\IIS Express\AppServer\applicationhost.config' to 'C:\Users\marko\AppData\Local\Temp\iisexpress\applicationhost201115151422496.config'
Temp configuration file settings error.
The system cannot find the file specified.
The instructions here are pretty weird especially the ones that deal with configuration file. As a matter of fact it says that the applicationhost.config should exist in Users Documents folder but there's no trace of it there.
I had the same problem.
It started working after I ran IIS Express by double clicking on the C:\Program Files\IIS Express\iisexpress.exe.
After that it worked when I ran it from the command line.
Yes, launching iisexpress.exe one time should fix the problem. This is a bug that we will fix at the earliest opportunity. Using the /path option uses a temporary configuration file under the temp directory, which is setup to include the specified app. Without /path, iisexpress.exe uses the default applicationhost.config under documents and will create one if it doesn't exist.
Hope this helps.