I am trying to start a workflow in my SharePoint 2013 provider hosted app.
The class I'm looking for is WorkflowServicesManager, however the dll Microsoft.SharePoint.WorkflowServicesBase.dll is not in the location I would expect.
Where can I get this dll from?
thanks
You can make a reference to file directly using it's location for Microsoft.SharePoint.WorkflowServicesBase:
%Windows%\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SharePoint.WorkflowServicesBase\v4.0_15.0.0.0__71e9bce111e9429c\Microsoft.SharePoint.WorkflowServicesBase.dll
I aslo wasn't able to get it usual way and had to reference file manually
Related
I am wanting to generate all of our application documentation using VSDocman and put them on Sharepoint. The act of uploading the finished documentation to Sharepoint isn't an issue and can be done fairly easily. The issue I have however is that VSDocman will not let me embed images in to the documentation unless I have the External Files Folder property set in its settings.
I want to set this property to be a child-directory on the sharepoint server where I place the actual generated documentation. So if my path is http://sharepointsite/documents/project1/docs, I'd want to place the directory in http://sharepointsite/docuemnts/project1/docs/images/
I'm not sure how to do that with Sharepoint. I have not been able to find any documentation online on how to basically connect to that sharepoint directory using a network drive or something that i can point VSDocman to. Anyone have any experience with trying to map to a sharepoint drive, without using the sharepoint workspace syncing? I need to basically have a filepath to the directory for VSDocman to use explicitly.
Thanks.
I was able to resolve this by mapping as a network drive using
\\sharepointsite\shared documents\project1\docs\images
In windows explorer. Once I figured out I could map to the drive, I just paste the same url in to VSDocman and attach the images that I needed. Worked like a charm.
I have a Visual Studio 2012 solution with many projects in it.
these projects all consume some Web-Services so all of them have References to some Web Url.
When I switch from Server to Server , I need to change all of these Url's.
I Know how to dynamically change Web References in final App, but keep in mind that these Web Services are in development environment , so are modified as a daily basis and it is hard to
change their Reference Url one-by-one in solution.
Is there a way to change all Solution's Web Reference Url's together ?
Regards, Saeed.
You could have a DLL that provides the URL and all the projects access that DLL to get the URL. That way only one file needs changing.
The URL could be provided via an environment variable, or a file in a defined directory, that each project reads when it starts.
The above two ideas might be combined. Have a DLL that reads the URL from a somewhere and provides it to the calling project. A clever DLL might know the difference between the machines that execute the tests and choose an appropriate URL.
There is also the Visual Studio editor, using menu => Edit => Find and replace => Replace in files.
I have a class library which searches for an XML file in the working directory of whichever application is consuming it.
It has worked as intended up until this point, when all of a sudden it's searching in the Visual Studio directory - C:/Program Files/Visual Studio 10/IDE/ - and thusly failing to find the file! I'm sure I've done something to cause it to do that, but I don't know what.
Does anybody know how I can resolve this, and get my library back to searching the proper directory?
EDIT: Could having a WCF service consume the dll have an effect, since the WcfSvcHost is in that directory? The dll has been consumed by WCF up to this point without this issue, however.
Whats you logic for getting the working directory? Also just as an (in)sanity check, have you tried moving the app round a few different folders to test the result?
Is it possible there is a version of your class library dll in that IDE folder that your app is picking up?
I have created a Silverlight class library which holds a lot of the common utility methods I use day to day in my Silverlight development.
I am starting to play around with Workflow and would like to reuse this common dll. After referencing this dll in my workflow project I see a yellow warning icon beside it.
I can use the functionality from this dll when creating ‘Code Activities’ without issue. After adding the using statement for it all works AOK.
using EquinoxeAISManagementSystem.Common.Helpers;
BUT when I try to import the dll from the activity designer, I do not see the dll in the import window.
If I edit the XAML and add it directly, I get a warning.
Is it possible to reuse Silverlight dlls?
I believe I can answer my own question.
The project EquinoxeAISMAnagementSsystem.Common is part of another solution. I had added this single project for the other solution into my new workflow solution (which I was having this issue in).
When I added the reference to the EquinoxeAISMAnagementSsystem.Common.dll initilly, it was by referencing the project in the workflow solution.
This seems to be the cause of the issue (for workflow anyway).
I was able to correct this issue by adding the EquinoxeAISMAnagementSsystem.Common.dll to a common folder where I keep all my external dlls (for ease of use).
..\Projects\EquinoxeAISManagementSystem.DLL\
I set up the output destination folder for this EquinoxeAISMAnagementSsystem.Common project to the folder above. I was then able to add the reference to Common.dll by browsing directly to the folder above.
Hay presto, all works.
I’m not sure id this is the ‘correct’ way to do things, but I needed to get over this hump.
I would be interested in anyone’s comments and if there is a correct(er), why to fix this issue.
Thanks ….
I am using VSTS Unitesting platform. I am trying to test a method which got references to assemblies which in turn contain DllImport to C++ DLLs.
In order for it to work I need to copy C++ DLLs to reside on the same directory the EXE and DLLs are running.
Of course when I use the same code with Unittest I also need to supply those DLLs.
I found out that the Unittest framework us using the $(Solution)\TestResults[WorkSpace] [DateTime]\Out as a working directory.
If I manually copy the C++ DLLs to this directory the unit test is is working like a charm.
The problem is that every time the Unitest is running it creates a new directory.
Has anybody encountered it? do you have a solution?
Thanks,
Ariel
As Steve D mentions, deployment items are the answer here. You can either put them on the class, or test method using the attribute, or use the Test Run Configuration to add them so that when any tests are run from that solution they will be deployed.
The other option is to make sure they're in the path somewhere so that the standard windows look up rules for DLLs will apply, and the runtime will be able to locate them.
Why is this a problem? because theres little to no metadata from the project to the Native DLL -- we don't know to pick it up. The only option really would be to dive all types in the deployed managed dlls looking for the DllImport attrib. This would, however, fail, if you are doing explicit DLLLoads in the managed code.
You could try using a [DeploymentItem] attribute. It allows you to specify a relative path from the solution file which will get copied to the test output directory.