I am following the Microsoft tutorial for creating my first sharepoint 2013 app.
(http://msdn.microsoft.com/en-us/library/fp142379.aspx )
I have installed on a windows 2008 R2 Server Sharepoint 2013 RTM, done all the farm config stuff RTM, and installed all of Visual Studio 2012 ultimate and update 1 and restarted the server.
I have also followed the instructions for "How to: Set up an on-premises development environment for apps for SharePoint" which is at http://msdn.microsoft.com/en-us/library/fp179923.aspx (I have to do this as our dev environment has no internet access)
I have got to the point where running Visual Studio as an Administrator I have named it and chosen "sharepoint-hosted" and validated the server and clicked finish (Step 5).
Instead of getting the next step where I open the AppManifest.xml file I get a message saying "An error occurred whilst trying to load some required components, Please ensure the following prerequisite components are installed. Microsoft Web Developer Tools and Microsoft Exchange Web Services"
I have checked VS setup and web developer tools is definetely installed (the only option I have would be to remove it)
Any help would be greatly appreciated. I know Im a noob here (this is my first post) but I have googled this and searched stack exchange and found nothing that helps me.
Got it after a few trial and errors
With an offline install you have to download the Exchange Web Services component. I had downloaded "EwsManageApi" and installed that.
As the error message specifically refers to Exchange Web services, I looked at other versions and tried the older 1.1 and the 32 bit version, but they didn't work either, ** until ** I relised in my haste that I installed using the default settings (which is for the current user) and not for all users of the machine.
So installing EwsManagedApi32 for all users on a 64 bit server does the trick (for me)
I tried reinstalling the EWS Managed API for All Users, but that didn't solve it for me. In the end the solution was simple:
Just uninstall BOTH the EWS Managed API and the Microsoft Office Developer Tools for Visual Studio 2012. After that reinstall ONLY the Office Developer Tools. This time the Web Platform Installer will ensure the correct EWS Managed API is also installed.
I also wrote a small blog about this problem:
https://leonzandman.com/2013/02/07/prerequisite-components-error-when-creating-a-visual-studio-2012-sharepoint-2013-app-project/
Answer for the year of 2014:
Install Microsoft Exchange Web Services Managed API 2.1 (the latest version I can find at this time).
Related
I have a client who has TFS 2010 and I need to setup my own installation on an Azure VM in order to do some testing, and help them migrate off of TFS 2010 to TFS 2015. However, I cant for the life of me seem to locate a setup .exe online for Team Foundation Server 2010. Is this still possible? Do I need a physical DVD?
The instructions here
https://www.microsoft.com/en-us/download/confirmation.aspx?id=24337
ask to use the physical DVD, but I dont have one.
According to this link https://social.msdn.microsoft.com/Forums/vstudio/en-US/56343ed9-6c0c-4c17-89d1-62b4bb3cf645/visual-studio-team-foundation-server-2010-setup-downloadable-link?forum=tfsbuild
Its available for MSDN subscribers, but I dont see any TFS versions below 2015 on MSDN download page.
I have found the service pack 1 install, but not the setup for the full product. can anyone help me locate a setup exe online so that I can get this running? Thank you in advance.
Seems you are installing TFS 2010 to simulate some existing environment and test configuration changes. However, there is not any setup.exe for TFS 2010 in official site for now.
It's unsupported and 8 years old. There have been five major releases since then. We encourage users move to newly version of TFS server. Either back up the TFS2010 database and do the move directly or use some other machine with DVD to install the TFS2010 ISO image for a test.
I recently setup a sharepoint server 2013 on our company and have found really good examples how you can override the suitbar with custom links.
Now that I'm trying to implement those examples i get to that point where Visual Studio 2012 and Office development tools is installed.
When i choose to start a new project I select New Project > Templates > Visual C# > Office/SharePoint > SharePoint Solutions > SharePoint 2013 Empty Project hit ok and i get an error that says Sharepoint not installed?
Am I supposed to install VS 2012 and develop om my Sharepoint 2013 server directly?
A very common way to develop SharePoint applications is to run a virtual machine (hyper-v under windows 8 for example) on your development workstation.
You can also dual-boot into a vhd file.
You can also install Windows Server 2012 and use one of the many desktop conversion techniques to use it as your primary operating system on your workstation.
Another often seen technique is to have a virtual machine hosted in the cloud or a datacenter, running both SharePoint Server and Visual Studio. Then connect to that machine using Remote Desktop.
With some trickery, you could have the SharePoint 2010 installer install om a workstation OS. This no longer works on SharePoint 2013. The reason this support was removed is due to the inclusion of Boot from VHD and Hyper-v into Windows 8.
It is my experience that if you just want to build your application and not run or debug it, that just having the assemblies copied over from an actual SharePoint Server will allow you to do that. I haven't found an updated document for SharePoint 2013 yet.
Yes. You have to develop on the sharepoint server directly using Visual Studio as Sharepoint server GAC has the required server object models to work programatically with sharepoint server object model.
You can aslo develop on client machine using Client Object Model or WCF Data Services Framework.
I have encounter to following error when I try to access "Manage TimeSheet" and "Project Center" page in my pwa site:
"Error
This Project Server 2010 feature requires at least Microsoft Internet Explorer 7.0.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 8f9f635b-c95b-4e2d-bd0a-e662c5d7b4ed"
I use Windows 8 (IE 10) and I have enable Compatibility mode.
This problem was first occurred when I installed and then uninstalled "Avant Browser" in my system.
I have read some texts that explain how this problem occurs and how to solve it.
Some of suggested solutions I have found are:
http://support.microsoft.com/kb/2394699
http://epmsource.com/2012/06/05/windows-8-release-preview-and-project-server-2010/
But unfortunately none of them solved my problem.
How can I fix this problem?
You have already added the URL to Compatability view, so I suggest to add the URL to local Intranet sites that solved the issue in my case.
For more details check Project Server 2010 requires at least Microsoft Internet Explorer 7
Did you change the User Agent as the links suggest?
I have also found that if there are restrictions or missing base Active X controls you may also get the "Error This Project Server 2010 feature requires...."
Not sure what they are but found that when trying to use the modern.ie virtual machines they would not work with Project Server 2010.
I know there are so many questions and articles on this topic and I have searched hours and hours on the Internet so far, but I still couldn’t find the right answer for my question. I was assigned the task to investigate the development environment for SharePoint web parts by my company. The money is not an issue but it must be the proper way to do it.
Here is my ideal plan: at developer desktop, install VS2005/2008 (it is already installed), VS2005/2008 Extension for SharePoint and WSPBuilder. It is also installed a Virtual Machine and the VM runs windows server 2003/2008. WSS3.0 and SQL Express 2005/2008 will be also installed on VM.
Developer’s desktop is a web parts development environment. Developers use VS to develop the SharePoint web parts and then run the WSPBuilder, it will deploy the web parts into the SharePoint testing environment on VM. So the VM is just a SharePoint testing environment.
It looks like a good idea, however, it doesn’t work. Why? Because VS extension can't be installed on developer’s desktop as it doesn’t have WSS3.0 installed!
I definitely don’t want to install the VS on the VM, because our developer desktop has installed VS and we don’t need to have 2 VS licences for 1 developer.
Any idea what is the best way to set up the development environment for SharePoint web parts?
Thank you in advance.
You won't be able to develop for SharePoint (WSS 3.0) unless your development environment includes an installation of at least WSS. In general, development is done on a Windows Server 2003 Virtual Machine (Visual Studio is installed directly on this machine). However, SharePoint can be installed on Windows Vista and Windows 7 machines, so your development machine may be able to host SharePoint itself, but it is far easier to do this on a VM.
My SharePoint development VM has the following installed:
Windows Server 2003 R2
SharePoint 2007 (Including SQL 2005)
Visual Studio 2008
Visual Studio Tools for Office
Office Server SDK
Visual Studio Extensions for WSS 1.3
Obviously you can use WSPBuilder instead, but I much prefer VSSWSS 1.3, but that is developer preference.
I believe (should be verified with Microsoft) that the licensing for Visual Studio can be extended to Virtual Machines when used by the same developer (depending on your agreement).
An alternative for you which may or may not work depending on your priorities.
Install Visual Studio 2010 and SharePoint 2010 Foundation to your development server.
Grab a copy of Microsoft.SharePoint.dll from a SharePoint 2007 server.
Use VS2010's tools to develop a web part but manually change the reference to the 2007 dll's (+ also see "Build a SharePoint 2007 Web Part with a Visual Studio 2010 Visual Web Part Project") so you are outputing a 2007 compatible web part.
When you delploy your 2007 web part to your local 2010 server it will just work (as its backwardly compatible)
When you deploy your 2007 web part to your test/qa/production servers it will work too.
Advantages
You're working with latest greatest
version of VS and the sharepoint
tooling so you get one click deploy,
automatic creation of WSP packages
etc. Nothing against WSP Builder etc (they are great) but my moneys on vs2010 sharepoint extensions for the future.
You're ready if/when your
company moves to 2010.
You're developing on a Windows 7 machine, not a 2003/2008 server and or a VM so this has advantages for licensing, speed and ease of use (dual monitor support from VS running on a VM?)
Edit - to deploy web parts to other servers you create a .wsp package and then deploy via STSSADM or another tool (SharePoint solution installer or other admin tools).
I haven't used VSSWSS or WSPBuilder. I've always used STSDEV for SharePoint 2007. And I've always used Windows XP to do it. I don't know if VSSWSS and WSPBuilder act the same, but, as Ryan was saying, I copy whatever SharePoint DLLs I need from a SharePoint 2007 server into a Solution Folder in my Visual Studio solution. I then select Add Reference in my project and browse to the DLL.
In four years, I've never had any problems with this method. The solution packages build just fine and work on any SharePoint server. I lose the option to debug, but I'd rather stay on my machine than go into a VM or Remote Desktop.
I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf file to the App_Data folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to
function properly. Please verify the installation of the component or download
from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
Uninstall all possible associated programs to Visual Studio, SQL Server or .NET Framework (which left .NET 2.0 Compact Framework and .NET 3.5 Compact Framework, and nothing else .NET related, installed).
Reboot.
Install .NET 3.5 SP1, SQL Server 2008 Express and SQL Server Management Studio 2008 Express via the Web Platform Installer 2.0 (Beta).
Reboot.
Install Visual Studio 2008 Professional from disc.
Reboot.
Install Visual Studio 2008 Service Pack 1.
Reboot.
Install hotfix.
Reboot.
Start VS, create new Web site and try to add database. Still get the error message...
When I look in the Help/About dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
Dave
Try changing the user on which the SQL Server Express is running. This can be changed in Services managment (press Win+R, type in services.msc). Choose SQL Server Express, right click -> Properties. 'Log On' tab and select: 'Local System account', tick the 'Allow service to interact with desktop' - this is what worked for me.
I'm not sure I ever solved this, but I've now moved over to Visual Studio 2010 (RC at the moment, but I'll get the full version when it's availabel) and everything works seemlessly.