Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I just installed the SharePoint SDK on my machine, but I can't seem to find the location of Microsoft.Sharepoint.dll so I can add a reference to it.
It's not in the GAC or C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\ and a search comes up with nothing.
Any suggestions?
Just FYI, I found it on the server where SharePoint was installed at:
E:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI
The dll is on the server where you installed SharePoint.
You should not develop on a desktop machine, create a virtual machine with SharePointserver installed and work there.
See: http://weblogs.asp.net/erobillard/archive/2007/02/23/build-a-sharepoint-development-machine.aspx
It might show up in the "add reference" dialog anyway - 99% of the time you don't reed to know the physical location. Look in the ".Net" list, which is sorted alphabetically.
I assume the SDK installer would assert this, but Sharepoint development also requires a server OS.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am getting this error everytime I open MS Excel / Word. I tried unchecking the checkbox "Ignore other applications that use Dynamic Data Exchange (DDE)" in Advanced options, but still I'm getting this error. Any suggestions?
i just feel like to share what worked for me as this thing really annoyed me for several months.
i researched on several websites/sources and all the solutions i have come across do not work. such solutions include but are not limited to:
1) clearing of the checkbox of that DDE thing.
2) registry edit (too risky for non-savvy PC users like me)
3) unchecking of "run as administrator"
but just recently, i uninstalled a program called Tune Up utilities and then the annoying error was gone. so what i would suggest for others is to check which programs do you think are incompatible with your MS Office. then uninstall that (those) program (s).
hope that helps.
best,
filousophe
Hey,
You need to deactivate all add-ins
http://office.microsoft.com/en-us/excel-help/enable-or-disable-add-ins-in-office-programs-HA010034127.aspx
one of them seems to be having an issue.
I solved it by right-clicking the document and choosing Open With... and noticed there were two Microsoft Word choices. I chose the second choice. And it worked and fixed the issue in the future.
If anyone can explain this in more detail, please do!
(I was using Windows 7 and Microsoft Word 2002.)
I came across this issue today. An update to the Office Compatibility Pack that was still on a computer caused the default program for .docx and .xlsx files to be the Microsoft Open XML Converter program and make the "Default Programs" in Control Panel think that Excel and Word were actually the Microsoft Open XML Converter program as well.
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
"There was a problem sending the command to the program" has appeared on my Windows 7 machine in the first week of September, 2013. I tried to repair MS Office 2003 from within the Program and Features, but repair and re-installation have failed due to "unspecified error". Windows application logs showed that the repair has failed due to "protected keys" in the Registry. Windows Installer was blocked from writing to MS Office keys. My antivirus and firewall were turned off. On the Uninstall or Change programs list I noticed September 6, 2013 entry "Microsoft Office 2003 Interoperative Assembly" from Microsoft. I didn't install this, so I uninstalled that item. Afterwards, both Excel and Word no longer showed an error, and files are opening normally.
KrysK
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
I am running Office 2013 - Win 7. Un-istalling the Compatibility pack for Windows 2007 AND rebooting, took care of my issue. After the reboot the .xlsx extension default is changed form XML converter to EXCEL. If you need the compatibility pack you may be able to just change the "Default Program" through Control Panel associated with the xlsx extension.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have successfully installed CruiseControl.Net server on windows 7 32 bit platform by CruiseControl.Net 1.8.0.0. setup file. But here there is no CCTray . Please let me know how to get CCTray.
Download it from official source (file is CruiseControl.NET-CCTray-1.8.0.0-Setup.exe):
http://build.nauck-it.de/download/CruiseControl.NET-package/1.8.0.0/
You can get it also from your CC.NET server.
If you go to the Web dashboard there is normally a link to download the tray.
Usually on the top right.
I had the same problem on CC.Net 1.5.x - installed it without IIS, and
found no Web Dashboard (to begin with). I wanted to control the CCNet Server.
I'm not sure if for 1.8 the CCTray application can only be downloaded separately from SF:
http://en.sourceforge.jp/projects/sfnet_ccnet/releases/
In my case, 1.5.7256.1, the installer for CCTray is there, in:
Program Files(x86)/CruiseControl.Net/webdashboard/cctray
You can install it after main CC.NET installation.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am getting this error everytime I open MS Excel / Word. I tried unchecking the checkbox "Ignore other applications that use Dynamic Data Exchange (DDE)" in Advanced options, but still I'm getting this error. Any suggestions?
i just feel like to share what worked for me as this thing really annoyed me for several months.
i researched on several websites/sources and all the solutions i have come across do not work. such solutions include but are not limited to:
1) clearing of the checkbox of that DDE thing.
2) registry edit (too risky for non-savvy PC users like me)
3) unchecking of "run as administrator"
but just recently, i uninstalled a program called Tune Up utilities and then the annoying error was gone. so what i would suggest for others is to check which programs do you think are incompatible with your MS Office. then uninstall that (those) program (s).
hope that helps.
best,
filousophe
Hey,
You need to deactivate all add-ins
http://office.microsoft.com/en-us/excel-help/enable-or-disable-add-ins-in-office-programs-HA010034127.aspx
one of them seems to be having an issue.
I solved it by right-clicking the document and choosing Open With... and noticed there were two Microsoft Word choices. I chose the second choice. And it worked and fixed the issue in the future.
If anyone can explain this in more detail, please do!
(I was using Windows 7 and Microsoft Word 2002.)
I came across this issue today. An update to the Office Compatibility Pack that was still on a computer caused the default program for .docx and .xlsx files to be the Microsoft Open XML Converter program and make the "Default Programs" in Control Panel think that Excel and Word were actually the Microsoft Open XML Converter program as well.
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
"There was a problem sending the command to the program" has appeared on my Windows 7 machine in the first week of September, 2013. I tried to repair MS Office 2003 from within the Program and Features, but repair and re-installation have failed due to "unspecified error". Windows application logs showed that the repair has failed due to "protected keys" in the Registry. Windows Installer was blocked from writing to MS Office keys. My antivirus and firewall were turned off. On the Uninstall or Change programs list I noticed September 6, 2013 entry "Microsoft Office 2003 Interoperative Assembly" from Microsoft. I didn't install this, so I uninstalled that item. Afterwards, both Excel and Word no longer showed an error, and files are opening normally.
KrysK
Uninstalling the Office Compatibility Pack in Programs and Features and then a simple reboot fixed the issue.
I am running Office 2013 - Win 7. Un-istalling the Compatibility pack for Windows 2007 AND rebooting, took care of my issue. After the reboot the .xlsx extension default is changed form XML converter to EXCEL. If you need the compatibility pack you may be able to just change the "Default Program" through Control Panel associated with the xlsx extension.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Ok first of all what is the difference between these two products?
Secondly are the development skills interchangeable between Server 2010 and Foundation 2010?
And lastly in terms of job market, when HR department writes "Looking for Sharepoint developer" do they mean developer for Sharepoint Server (MOSS) or Sharepoint Foundation (Services)?
Note: Working with SP Foundation would be better in my case because Sharepoint Server 2010 brings my computer to its knees with only 3GB RAM. Sharepoint Foundation is it a good starting point or would you suggest going with Sharepoint Server?
Strictly speaking, SharePoint Server IS SharePoint Foundation with additional features. Therefore, all your SharePoint Foundation development skills can be used in SharePoint Server as well. What you should/could use depends on the requirements of your project. Some projects require features that are only available in SharePoint Server, so that narrows your options.
If your PC is not powerfull enough to run SharePoint Server, there's always the option to install it on a development server and connect to it remotely. That is... if you have a development server available.
Side note: the term MOSS is only used for SharePoint Server 2007. Microsoft decided to change the name of the product from Microsoft Office SharePoint Server to Microsoft SharePoint Server.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm curious to know how other SharePoint developers setup their dev workstations.
My current setup:
Desktop with Server 2008 (only for Hyper-V, was using Vista before)
Use Visual Studio 2008 on local machine for dev work
Keep a local copy of SharePoint DLLs for referencing, no local SharePoint install
Run SharePoint in a Server 2003 VM hosted on my local machine
I develop all my SharePoint changes as a WSP and install them into the VM for testing. I don't run code in debug mode, but do write lots of trace statements to watch what my code is doing.
Also, when I'm making quick changes, I normally don't reinstall the entire WSP. I just recompile whatever DLL I changed and copy it into the GAC in my SharePoint VM, then reset IIS (normally writing Web Parts).
I know things would be easier if I ran SharePoint locally, but I'm normally working on more than one project at a time and don't want things to interfere.
Definitely prefer working in VM with SharePoint directly as I can debug into processes correctly, also I have a build script that will either redeploy my entire solution or let me just refresh the GAC.
I do all my development work on one of my VMware images. Since I try to do my SharePoint work in a TDD style I run a lot of tests and then the remote stuff just don't make sense to me.
The single item that have helped me the most is the post build event in visual studio, it is really amazing all the things you can do with a bit of scripting.
Running SharePoint/VS on the same server (either physical or virtual) will get you up and running quickly, but personally I don't think its the way to go.
In addition to what you describe (local VS/SharePoint running in VM's) then a few tips that may make your life easier.
1) Deploy to the bin directory rather than the GAC, then to update all you have to do is copy over your dll/pdb's in a post build batch file - don't think you can do that automatically if they are in the GAC on a remote machine can you?
2) Look at remote debugging - it can be a little bit of a pain to get working first but the effort is worth it! key tip is you need to use the same username/password on both the local and remote machine.
This page is related -
Debugging SharePoint 2007 Code