I'm trying to create a custom process template in Azure DevOps Server 2020. I'm using the on-premises XML process model. When I upload my custom process template I keep getting 'You can't update a system process' error.
These are the steps I took:
Downloaded the Agile system process by going to Collection Settings->Process, clicking on Agile and choosing 'Export'.
I unzipped the downloaded folder and opened it in Visual Studio.
I made changes to field names and added new states for bugs.
I changed the name and version in the ProcessTemplate.xml like so:
<metadata>
<name>CustomProcess</name>
<description>This is a custom process template based on the Agile process</description>
<version type="ADCC42AB-9882-485E-A3ED-7678F01F66BC" major="1" minor="0" />
I renamed the folder to CustomProcess and zipped it.
In Collection Settings->Process, I clicked on 'Upload process template' and tried to upload my CustomProcess zipped folder. I get the error 'You can't update a system process'.
I made sure to update the name and version as suggested in a previous Stackoverflow post but I still get an error. Is there something else I need to modify in the XML files?
Check this answer: https://developercommunity.visualstudio.com/content/problem/310354/cant-upload-a-custom-process-template-to-tfs-2018.html
You have to change the name and the version of the template
I looked at some more related Stackoverflow posts and found this one helpful. The issue was I need to generate a new GUID for the version. I went into Visual Studio, go to Tools -> Create GUID. Choose the number 6 option for the GUID format. Paste the GUID into the version type: <version type="[paste GUID here]" major="1" minor="0" />
Hopefully this will help someone else with a similar issue. The official documentation doesn't mention any of this which is very disappointing.
Related
I've added a webjobs sdk project to my existing website. The website runs as an azure app service. I've always done building and deployment by queueing up a new build in visual studio online and deploying from there to my azure website. Recently I created this webjob project in the same solution, that based on this webjobs-list.json generated and put in the website project should cause the webjob to also be deployed with the website during deployment (or so the documentation says). What is happening though is that when it deploys, and I take a look at what is in app_data\jobs\continuous, is not the binaries and executable that I expect, it's the actual source code/project files that have been copied into there. Obviously that isn't going to run, and it shouldn't have thrown source code out there on my website anyway.
I also had to change my release definition in visual studio online to just look for [my website project name].zip, instead of just *.zip, because otherwise I'd get an error from the release indicating: Error: More than one package matched with specified pattern. Please restrain the search patern.
...this appeared to be because the build process not only creates a zip file for my website, it also creates one for the webjobs project. From what I understand and have read, I am supposed to change my release to just look for the website zip file and ignore the other zip file, and just let that get deployed and it should all work fine, but again, what is copied into my jobs folder on the website isn't the binaries or executable for the webjob, it's the actual source files.
How can I get this to deploy just the binaries and executable with the site instead of the source files?
The only other thing I could find to do is remove the webjobs-list.json file from the web project so they are no longer linked together, which causes the build to no longer populate app_data\jobs\continuous with my web job project source files when deployed, and to create an additional task in my release definition to grab and deploy the other zip file that is created during the build (for the webjob project, and it contains the debug files with those binaries for whatever reason). However everything I read tells me that this is not supposed to have to be done, it should just work without me having to do this.
EDIT:
My web project is an MVC 5 project that I created with VS 2013. The web jobs project uses the 2.0.0.0 version of the webjobs sdk.
The build and release definitions, I followed the steps in this article to create:
https://www.visualstudio.com/en-us/docs/build/apps/cd/deploy-webdeploy-webapps
The only additional thing I did after following this article, is in my release definition, I changed the Package or Folder field to look for [my mvc web project name].zip, instead of *.zip, otherwise I'd get the error message noted above.
I have a simple web application in Visual Studio 2015.
With the Azure SDK installed, when I right-click the project and select Publish, I get a UI that allows me to select Microsoft Azure App Service as a publish target.
If I sign in and walk through the wizard, I ultimately end up with .pubxml and .pubxml.user files in my project that have the user names passwords, deployment endpoint, etc. that I need.
I am looking for a way to do this from the command line (ideally with PowerShell cmdlets for Azure, but calls to MSDeploy.exe or MSBuild.exe would be just fine).
Msbuild(Msdeploy) does not have related argument to create .pubxml and .pubxml.user, if want to use command line to achieve, you need to create a custom task, which create the xml by using code (C# or other). And you need to know the xml structure and related content.
About custom task, please refer to:https://blogs.msdn.microsoft.com/msbuild/2006/01/21/how-to-implementing-custom-tasks-part-i/
About create xml via c#, please refer to：https://msdn.microsoft.com/en-us/library/ff604982.aspx
I'm trying to setup Microsoft reporting on a shared hosted server. I've set up the web.config files with the necessary entries and uploaded the assemblies Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll as well as the file Microsoft.ReportViewer.xml via FTP.
The site loads OK, but when I try to load a report a get a missing reference to Microsoft.ReportViewer.ProcessingObjectModel.dll. If I can get a hold of a copy of this dll, can I expect the report view to work? If so, what's the best way to get a copy? Or should I start trying to cajole the server administrator to run ReportViewer.exe?
This project is using Visual Studio 2008.
It appears that the answer is yes. I had never extracted a file from the GAC before, but it was pretty easy by following the command line method described in this question. Once the correct version of Microsoft.ReportViewer.ProcessingObjectModel.dll was extracted from the GAC on my development machine and uploaded to the site, the reports started working.
I'm new in Infopath developing, please help. :(
So I'm developing work-flow with custom task edit form.
I designed infopath form CustomApprovalForm.xsn in Infopath Designer 2010 and then I published this form to Workflow project in Module folder which named Form(ApproveWF/Form/).
Then I configured all needed properties for correct deploying. After deploying all works ok and form appears as it should be.
But when I come back to Infopath designer 2010 and add some formcode to CustomApproval.xsn and then I press quick publish to Module folder which I use above and then I deploy the workflow to SP server.
After this the form doesn't appear.
In logs I saw exception:
"Solution deserialization failed with unhandled exception
System.IO.FileNotFoundException: Could not load file or assembly
'file:///C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\14\Template\Features\ApproveWF_Feature1\CustomApprovalForm.dll'
or one of its dependencies. The system cannot find the file
specified...."
I suppose, that I'm not correct making publishing infopath form with code behind.
How to correct do publishing infopath 2010 form with code behind to my ApproveWF project which then deploy to SP server?
Where should I place the CustomApproval.dll?
Please help me!!!!
I believe, but I'll have to double-check, that what happened is that you did a full publish first with no code behind the form - this registered the manifest, which did not include a reference to a .dll, since there wasn't one.
You then added code, which gets compiled into a dll, listed in the manifest for the form.
I think when you do a quick-publish, the form files are copied up to the server, but the manifest isn't re-registered. So the form xml/xsl will have calls to the dll, but the manifest won't know where to find it, since it wasn't updated.
tl;dr: when you publish a form then add code to it, you have to run a full publishing cycle again to update the installed manifest.
Post a follow-up if this doesn't work.
I've found the solution.
I have to add new item to Workflow project which named Empty Element. And then I've added dll of xsn CustomForm to it. And then I've deployed this dll with xsn form like feature to sharepoint.
I have created a web part using VSeWSS 1.3. It creates a wsp file and my web part gets installed, everything works great.
I would like to also create a folder in the LAYOUTS directory of the 12 hive and place a couple files in there. How do I go about doing this? I know that I can manually place the files there, but I would prefer to have it all done in one fell swoop when I uses stsadm to install my solution.
Is there a best practices guide out there for using VSeWSS 1.3 to do this? They changed a bunch of stuff with this new version and I want to make sure I don't mess anything up.
You can create a new folder structure in your webpart project, like:
Templates/Layouts/CustomFolder and put your files in the CustomFolder directory and include them in your project.
When you go to the WSP View in Visual Studio, you can see in the manifest.xml that your files are being included in the deployment.
I have done this successfully on multiple projects now.
In case anyone is wondering, the VSeWSS 1.3 user guide is incredibly helpful. It is installed to the same directory as the tool itself, default in C:\Program Files\Microsoft SharePoint Developer Tools 9.0\VSeWSS13.CHM
You can see a working example with screenshots Here
A simple step-by-step tutorial for the above, along with deploy/retract scripts is here at Add New Files To 12-Hive Through A SharePoint Solution. Just follow the steps and in a few minutes you'll be able to add whatever you want to the 12-Hive!