I am currently writing a Windows application in C# that will add documents to a document library list. I am trying to reference Microsoft.Sharepoint, however I do not see the COM or .NET library inside visual studio 2005 add references lists. What dll do I need to reference and where can I find this?
Thanks,
Alex
To access a document library I would recommend going through the list web service which SharePoint exposes. From personal experience that is the easiest, most portable and upgradable way.
The documentation for ALL the web services and .NET libraries to do it as well can be download in Visual studio extensions for windows sharepoint services
to access the SharePoint library you have to include following assembly into your project: Microsoft.SharePoint.dll
You can find it on your SharePoint Server under the 12 hives folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI
There you can find some more assemblies you might need for more SharePoint functionality.
What kind of application do you have to develop???
If it is a client application that will be execute on machines that are not the Sharepoint target machine you'll have to call to SharePoint web services to do the operations.
If your application will be executed on server, SharePoint machine, you can use the dll's that are on 12 folder. For developing, you'll have to copy the dll's on a local folder and reference them into your project. To check if the application works well have to be executed on the SharePoint machine not on the developing machine.
I assume you're using Sharepoint 2007, so you are able to find the libraries in the Bin folder in the 12 Hive on where SP is installed. That is usually:
C:\program files\common files\microsoft shared\web server extensions\12
You will need a reference to Microsoft.SharePoint.dll.
Related
I'm writing some integration my program which uses an ODBC dll on Visual Studio Online. The VSO provides Hosted Build Controllers so that I don't have to set up my own TFS server. However, to use the ODBC dll you normally have to install it for which the Hosted Build Controllers don't give me that permission.
Just wondering if it is possible to bypass the installation and load up the dll directly in some way?
Couldn't find some information about that anywhere.
Its an Asp.net website . Running good on local development system . VS2010 and .NET 4 . When uploading to web server it throws an assembly could not be loaded error in my web.config file .
I sort it on google by changing framework from 3.5 to 4 will arise this error . My doubt is there any way to lock or persist the integrity of an assembly file through out the .NET versions .
My hosting server URL : http://ananth7453-001-site1.mywindowshosting.com/
Thanks for your time
VSLangProj80 is installed as part of Visual Studio which is why your site works on your development machine. Copy the DLL to your project folder and then replace the reference in Visual Studio with the copy.
On my machine VSLangProj80 is located at C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\VSLangProj80.dll
I want to share the solution I encountered as I have the same issue encountered. Over the years, our web server is installed with different Visual Studio programs, such as Shell (integrated mode) and Tools for Applications 2.0 ENU. There's also Tools for Office Runtime. It took us a while to isolate which of these installs conflicts to the application we are trying to install.
We found out that our application has the latest version of VSLangProj80.dll and the one in our server is using older version. Without changing our build since it is working on our UAT environment, we manage to un-install the Tools for Application 2.0 ENU. Removing this one out of our production server resolved this issue.
I developed a site in asp.net using C# as the language.
I have debugged it and no more errors can be found and can also view the page from a browser.
I would like to host this site and direct a client to it for demo purposes but am having a problem each time I publish my site. The publishing only does away with all my .aspx.cs files but I don't see any .exe file that I can install or send to my hosting provider.
I would like to know if this what I am experiencing is normal or there are settings I need to do in my visual studio 2013 ultimate edition for these tasks to be performed?
Kindly advise me on the way forward
ASP.NET applications (not "ASP.NET websites") are compiled into a .dll file in your bin folder, which is then deployed on to the server.
Your .aspx/.cshtml1 files reference compiled classes and types contained within this DLL, thus eliminating the need for source files.
There won't be any .exe files, you need to deploy your project to a web server, like IIS. Check out this link.
First off, I would like to say that I am very new to SharePoint and SSIS.
I'm trying to create an SSIS package in VS2010 that fetches rows from a remote SQL server and pushes it to a (also remote) Sharepoint Library.
So far, I managed to install and use the Business Intelligence to design the SSIS package on my VS2010 (thx to SQL server 2012 Standard 180-trial version).
I've also found out about the SharePoint List Adapters, but from what I've read, they are only usable in VS2008.
So, I want to find out if:
1. Is it possible to achieve this (SQL -> SSIS Package -> Upload/Push to Sharepoint)
2. Can I use SSIS SharePoint Tools in VS2010?
3. (Edit! Important) Is uploading Shared Documents in SharePoint Library achieved in the same way as publishing lists ?
I've found a (not so pleasing) answer to my #1 question, and it's from 2011, so I hope maybe some solution has come up since then: Sharepoint Development in Visual Studio 2010
Disclaimer: I don't know much about SSIS.
However, if SSIS lets you "run a custom piece of code for each SQL returned row", you could then use the SharePoint 2010 Client Object Model to create a SharePoint list item on a remote server for each SQL row.
This doesn't require SharePoint to be fully installed on the machine running the SSIS code. It only requires a couple of DLLs, Microsoft.SharePoint.Client.dll and Microsoft.SharePoint.Client.Runtime.dll. You can copy these from a SharePoint server (located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI) or, I believe, you can install the SharePoint Foundation 2010 Client Object Model Redistributable.
I am developing on a 64bit version of Windows 7, running MOSS (SharePoint), this is my dev machine.
Now when I deploy my web service app to a test server Windows 2003 32bit (no Sharepoint installed) I get this error.
Could not load file or assembly 'Microsoft.SharePoint.Library, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified
The DLL has clearly been copied to the bin directory (Microsoft.Sharepoint.dll).
Any ideas?
If you are using sharepoint dll's it will only work on a machine with sharepoint installed.
Even if you managed to hack it and get it to work, you would probably be breaking a license agreement.
There is a way to load Sharepoint libraries in a development console with windows XP, Vista or Seven.
See here: http://fernandof.wordpress.com/2008/02/11/how-to-install-the-sharepoint-2007-vs-2005-extensions-on-a-workstation/
[O]pen the regedit and create the following keys and the string value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]
"Sharepoint"="Installed"
That’s it! You have fooled the installer into running on a
workstation. Easy. I also recommend adding the core SharePoint
assemblies into the [GAC] using gacutil. Those assemblies can be found
by default in any [SharePoint] machine under the folder: C:\Program
Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI.
This is almost certainly a dependency issue. The DLL is dependent on another DLL which isn't in the GAC or on the probing path. The two tools you need to figure this out are FUSLOGVW.EXE and Process Monitor
Fusion Log viewer will allow you to look at assembly bind successes and failures as your application loads. It's part of the Windows SDK.
http://msdn.microsoft.com/en-us/library/e74a18c4(VS.71).aspx
FUSLOGVW needs admin privs to run correctly.
If that doesn't work another tactic is to use Process monitor to look at which files aren't getting loaded and which folders are being searched.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
However. Without SharePoint installed I wouldn't expect this to work.
Ade
From MSDN:
"The CI build environment for the Training Management application does not perform any tests that require a live instance of SharePoint. All the unit tests use mocks that replace the actual SharePoint instance and services. Building the code and running the unit tests only requires that the following SharePoint assemblies are installed on the CI build server:
Microsoft.SharePoint
Microsoft.SharePoint.Security
Microsoft.SharePoint.WorkflowActions
Supporting referenced assemblies"
http://msdn.microsoft.com/en-us/library/ff647619.aspx
Don't mix 64-bit and 32-bit for dev / testing / production. This will never work reliably if at all.
Well what about other dlls referenced by the Sharepoint dll? With long dependency chains it can be quite difficult to diagnose these sort of problems. In such situations I find the fusion log viewer extremely useful. It is a part of framework SDK - open the SDK Command prompt and type fuslogvw. It is pretty obvious from there