I'm attempting to deploy ODP.Net with my application using the Oracle Instaclient. While reading the instructions on this site (Deploying ODP.Net with Oracle Instant Client I see where it says the following: "In subdirectories of ODP.NET20 locate and copy OraOps11w.dll and Oracle.DataAccess.dll to your deployment directory". The question I have is, "Where is my deployment directory?" At this point, I haven't deployed my application, so no deployment directory has been created. Is this article talking about copying the files to my project directory? Or do I need to manually create a deployment directory to copy these files to?
It's arbitrary - put them anywhere. In fact you don't need to copy them at all. You could just add them to your install project from their current location. It just recommends copying them to "your deployment dicrectory" so that you can then delete the whole package from that you extracted, since you've got what you need.
Related
I have the below structure in ssis server:
Assuming I worked on Integration service project in VS but only on one dtsx from the list above.
Now I ran the below SSISDeploy (documentation is here) command from CMD:
SSISDeploy.exe -s:"C:\git\test\Integration Services\bin\Development\Integration Services.ispac" -d:catalog;/SSISDB/TEST/TEST_INRG;"TEST03,1234" -at:win
and got this message:
Will deploy 'Integration Services.ispac' to TEST03,2890:/SSISDB/TEST/TEST_INTG.
The project 'TEST_INTG' already exists in the catalog folder 'TEST'. Will overwrite it.
So what actually happened, all the packages were delete and my dtsx package was overwritten the modified one. Is there a flag which can tell the command to change only what was modified? I was expecting to see only change in the actual dtsx package.
Got official answer in Microsoft forum:
https://learn.microsoft.com/answers/answers/441954/view.html
I have a requirement to publish a .net desktop application to an on-prem machine which I have now installed VSTS agent on successfully registered. The VSTS release can see the machine OK and it works until downloading the artifact.
I have below settings for Copy files in the Release Definition:-
the settings for Publish Artifact task is :-
I want to copy the build output to a local folder on the designated machine. When release process starts, the artifact is copied to the local machine under vsts work folder OK, however, when the Copy Files process start, it fails with error can't find the folder.
while this folder is available there on C: drive.
Any help is much appreciated.
thanks
Publish Artifacts is the wrong task to use for this. That's intended to be used in your build process.
Just use Copy Files.
We have used the following TFS Deployment strategy used for Websites -:
1) Windows Machine File Copy
Source : Folder of TFS
Target : Application Server
Now, in a folder placed inside this website, files are first deleted and then added/ re-created.
But after deploying through TFS, files are made Read-Only. So files can't be deleted and error is thrown on the website.
How to handle this case in TFS deployment
I'm assuming your build a server workspace or you are directly pulling files from TFVC into a server workspace (see local vs. server workspaces). In a server workspace files that are not check-out are read in the workspace to prevent you from making changes locally without first telling TFS you are going to changes them (check-out). Since your build will usually not perform any source control operations in your workspace some or or all files remain read-only when you copy them or publish them as artifacts.
If you copy items from TFS to another location these read-only flags are also copied. However this is easily fixed by using attrib -r to clear the read-only flag either before publishing the artifacts from your build or before (or after) copying the files over to the target machine. See the attrib documentation for more options like recursion.
When you set a folder path as the Physical Path for a website in IIS 6.0, you will see that the folder are made to Read-only automatically.
You could remove the Read only setting for this folder in the folder property. If you want to remove the read only setting for your folder. In the Windows Machine File Copy step, you need to provide an account which is the administrator of the target machine.
Problem has been resolved by adding one attribute of Windows robocopy command.
/A-:R : Removes the Read only attributes from copied files.
"/A" : attribute
"-" : remove
"R" : Read only property
I am trying to create a deployment package in Visual Studio 2013. I have specified that the package should be placed at C:\Deployment\bin\WebSite.zip - the absolutely simplest location. All the project files build but the publish fails with this error:
Transformed Web.config using C:\Services\IdentityServer\Thinktecture.IdentityServer.v2\src\OnPremise\WebSite\Web.Siloed.config into obj\Siloed\TransformWebConfig\transformed\Web.config.
Auto ConnectionString Transformed Areas\Admin\Views\Web.config into obj\Siloed\CSAutoParameterize\transformed\Areas\Admin\Views\Web.config.
Auto ConnectionString Transformed Views\Web.config into obj\Siloed\CSAutoParameterize\transformed\Views\Web.config.
Auto ConnectionString Transformed obj\Siloed\TransformWebConfig\transformed\Web.config into obj\Siloed\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Siloed\Package\PackageTmp.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(2584,5): Error : Copying file ..\..\..\Deployment\bin\um.zip to obj\Siloed\Package\PackageTmp\.ebextensions\um.zip failed. Could not find a part of the path '..\..\..\Deployment\bin\um.zip'.
I have no idea where this path '......\Deployment\bin\um.zip' is coming from. I specified that the deployment package should be created at C:\Deployment\bin\WebSite.zip, not um.zip.
So, I checked out C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(2584,5) and the code looks like this:
<!--Force Copy Of all file to the $(WPPAllFilesInSingleFolder) if needed-->
<CopyPipelineFiles PipelineItems="#(FilesForPackagingFromProject)"
SourceDirectory="$(WebPublishPipelineProjectDirectory)"
TargetDirectory="$(WPPAllFilesInSingleFolder)"
SkipMetadataExcludeTrueItems="True"
UpdateItemSpec="True"
DeleteItemsMarkAsExcludeTrue ="True"
Condition="'#(FilesForPackagingFromProject)' != ''">
<Output TaskParameter="ResultPipelineItems" ItemName="_FilesForPackagingFromProjectTempory"/>
</CopyPipelineFile>
I have tried editing the "PipelineItems" and "SourceDirectory" and have even hardcoded them. But the same message, "Could not find part of the path....", is being displayed every time I run the Publishing. The "Could not find part of the path...." points to the new paths I specified in "PipelineItems" and "SourceDirectory. The .zip file never seems to get created anywhere. I have seached my entire computer for um.zip and WebSite.zip with not luck.
Any help would be greatly appreciated as I am completely out of ideas.
Turns out this um.zip is somehow part of build but it is not getting created. Anyway, I was lucky enough to find a previous deployment package that was generated and I just manually built the new deployment package based off the old one. Deployed fine so I guess that is how I will proceed.
Is there a way in teamcity to restore a deleted build configuration. I found Restore just deleted project which is about restoring a deleted project but can't find any information about restoring a deleted build configuration. I am using Teamcity 8.0.6
TeamCity 9, locate your data directory and you'll find a trash folder, like so:
D:\TeamCity\Data\config\_trash
Take a copy of the whole thing to some other folder, just in case.
Move the effected project folders from config\_trash to config\projects.
Remove the suffixed .projectNN from each project folder.
You may see critical errors in the main web portal while this is happening.
Restart TeamCity just for good measure.
The previous versions of build configuration setting are stored in /config/projects/buildTypes folder in different *.xml.N files. To restore setting replace *.xml file with *.xml.N file.
Also since TeamCity 9 it is possible to store all project setting in VCS.
Another option, available since 9.0 is to place project settings in version control (Git, Mercurial, or Subversion and Perforce since 9.1), and then restore removed files using VCS commands.