Sharepoint 2013 Farm Visual Studio cannot connect - visual-studio

I have Visual Studio Ultimate 2013 and SharePoint Designer installed on my local machine. I have a SharePoint installed on a server farm that i have full read and write permissions on. My problem is when i try to create the project the wizard to connect to the SharePoint will not show up and it says i need it installed on my local machine. I have read many forums posts such as
https://social.msdn.microsoft.com/Forums/en-US/5853a07e-e033-43ab-929b-f5766354fea9/cannot-connect-to-sharepoint-2013-farm-with-office-tools-for-visual-studio-2012?forum=sharepointdevelopment
https://msdn.microsoft.com/en-us/library/office/jj220047(v=office.15).aspx
along with others these are just the ones still open in my browser. I would love some help or a proper tutorial because the ones i am finding are no help and im not seeing anything besides a error message saying i cannot create a project until i install foundation or server for sharepoint

This is a case where the error message means exactly what it says. You must install SharePoint on your development machine in order to use Visual Studio for local SharePoint development. You can develop on Windows Server 2008/2013 (most common solution I've seen), install SharePoint on your Windows 7/8 machine (which is painful to do but possible), or set up a remote environment for development after signing up for an Office 365 Developer Site.

After hours of searching I found a work around for anyone who is running into this problem... You need to make a web reference to the SharePoint site then you can access the XML and do it that way. Microsoft hides the option its under service reference then you click web reference add the URL and a easily called name add it and your good to go.

Related

Develope Sharepoint solution in VS2010 in Development machine and sharepoint 2013 in Server machine

Am very new to Sharepoint , i installed the VS2010 in development machine and Sharepoint 2013 installed in Server machine. now i have to Develope Sharepoint solution in VS2010.
but in sharepoint wizard,
it asking the site and security for debugging :i have given the my site in textbox which running in my local machine. and when i validated that,
am getting the
SharePoint Connection Error
---------------------------
Cannot connect to the SharePoint site: my site. Make sure that the Site URL is valid, that the SharePoint site is running on the local computer, and that the current user has the necessary permissions to access the site.
Additional information:
A SharePoint server is not installed on this computer. A SharePoint server must be installed to work with SharePoint projects.
**Am one of the active directory user
**I have the privileged to access my site what i created in Central admin
**VS 2010 installed in Development machine, sahrepoint 2013 installed in server machine, am using the sahrepoint , by sharepoint dll installed into GAC in to develpment machine.
any one come across this problem and know the solution for it. ?
Thanks in advance.
The error says:
Make sure that the Site URL is valid, that the SharePoint site is running on the local computer
You need to install SP2013 on your dev enviroment.

Frontpage server extensions install problem

Here is the antenced of my story
I've got a problem with the VS or IIS. I don't know.
When in the Visual Studio 2010 I try to create website: throw up the follow errormessage:
Unable to create the Wet site'http://www.ecommerce.com'. The Web server does not appear to have FrontPage Server Extensions installe.
I download the Frontpage extension from here: http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1630
Then I read how can it install, but when the article write that:
To extend a Web site using HTML Administration pages on Windows, use the following steps:
Click Start, point to Programs, point to Administrative Tools, and then click Microsoft SharePoint Administrator to open the Server Administration page.
In the list of virtual servers, click Extend next to the virtual server you want to extend.
In the Administrator box, type the user name for the administrator of the virtual server.
Click Submit.
I don't find Microsoft SharePoint Administrator on my Windows 7 Profesionnal 64 bit
or
You can extend a Web site by using the command-line tools, owsadm or owsrmadm. These tools are located in the "%ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\50\bin" folder. To extend a Web site, use the install operation, which takes the following parameters.
I don't find the Web Server Extennsions dir on my Windows 7 Profesionnal 64 bit
I have read another article where write that, Use the Visual Studio DVD go to WCU dir and into the Web Server ... dir, but I don't find...
I download the FPSE and install with my local Administration account.
But the Visaul Studio Always says: The WEb server does not appear to haver FPSE installed.
How can I fix it? Install it?
Bad news (may not be so bad): FPSE for IIS 7 and 7.5 are not supported. Alternative is to use WebDav and here's an article explaining how to migrate FPSE Sites to WebDAV.
Good News (may not be so good due to licensing part): As of December 18, 2010, Ready-to-Run Software Inc. has created Microsoft FrontPage Server Extensions (FPSE) 2002 for IIS 7 and 7.5.
See this announcement from MS: FrontPage 2002 Server Extensions for IIS 7.0 on Windows Server 2008 and Windows Vista
If the FrontPage Server Extensions are installed, this error may occur because the _vti_bin virtual directory is not marked executable. To correct this problem, run the Internet Service Manager, select the Web server having the problem, and use the Check Server Extensions task. Reference: http://msdn.microsoft.com/en-us/library/aa984224%28v=vs.71%29.aspx

Building webparts with Visual Studio 2010 Express

I'm trying to get started with building my own webparts, planning to follow this MSDN article.
I've downloaded Visual C# 2010 Express - I'm not quite at the point where I feel comfortable dropping 1000 big ones yet, and I installed Visual Web Developer 2010 Express via the WPInstaller.
Following through the tutorial, aside from the fact that I don't get the option to create a "Web Control Library", a gap I filled with this article, I can't seem to find the sn.exe tool (or the "Visual Studio 2005 Command Prompt"!).
I know it's not quite a direct programming related question, but I can't even get the thing going yet!
Any help is appreciated.
Thanks
EDIT:-
I think I may be jumping the gun quite considerably, I wrote a simple hello world example and tried to build it but it doesn't have any references to the Microsoft.SharePoint packages and they don't appear in my lists.
Am I understanding some more research I've done (namely this) correctly, in that I have to actually have a full installation of actual SharePoint on the machine I'm developing on?
sn.exe is part of the .Net Framework SDK tools - not actually part of Visual Studio.
If you've got the SDK installed (which I think you must have if you're using VS) then it will be in a directory such as (depending on which version of .NET SDK you've got installed)
c:\program files\microsoft.net\SDK\v2.0\Bin
You can develop SharePoint web parts with VS express but you won't be able to use extensions like VSeWSS which can make your life a little easier.
You don't have develop on a machine with SharePoint installed upon - you can just copy the Microsoft.SharePoint.dll assembly from a machine with it installed on and reference it in your project.
There are pros and cons to developing on a SharePoint machine.
Its easier to get started -
especially debugging locally rather
than remote debugging.
Harder to be
sure that you're code will work a
'real server' - are you sure you
don't have any dependencies that may
not be installed.
Harder to work with
multiple versions of SharePoint (2007
WSS and MOSS and 2010 foundation,
server etc).
If you do want to work with a locally installed SharePoint then
You can install windows server OS with SharePoint and Visual Studio.
there is a hack for installing SharePoint 2007 on vista (referenced in the SO article you link to)
you can install SharePoint Foundation 2010 on Windows 7 (but I am not sure what the licensing restrictions are - is this maybe something thats given through MSDN?)
If you decide to go with the remote server installation then save yourself some grief and use virtualization such as VMWare Server, Virtual PC or Hyper-V.
If you are doing SharePoint development trying to reference the Microsoft.SharePoint namespaces you need to have SharePoint installed on the machine if you want to do things like debugging, etc. For SP 2010 you CAN install SharePoint on a Win 7 machine. For previous versions of SharePoint, you will need to setup a Server that is Server 2003 or Server 2008 (you can't install SP 2007 and earlier on client machines). Generally this is a Virtual Machine for developers.
Having said all of that, there are relatively few reasons you need SharePoint to develop a WebPart. The vast majority of the WebPart functionality is part of the System.Web.UI.WebControls.WebParts namespace. Even if I am accessing SharePoint data, I generally use the ASP.NET web part.
If you are trying to use the new SharePoint VS 2010 functionality to create Visual Web Parts, etc, then you will need to install SP 2010, since that functionality is not supported in earlier version of SharePoint.
John

Web Access in Visual Studio 2010

I try to upgrade a plug-in that was on webaccess 2008. Whe were using WebAccessSession to get the user name of the current user logged (WebAccessSession.Current.Connection.UserName ). I Imagine now that it is in tfsConnection but I'm not sure.
Is there any documentation that tells what really changes between Team Foundation Server 2008 and Team Foundation Server 2010?
No documentaion that details things at the level that you are looking for I'm afraid. As far as I know, plugging in to Web Access is not supported via any specified API so any integration you have done yourself would be classed as unsupported so you'd be on your own when it comes to figuring those sorts of changes out. Sorry.
As far as your question about Web Access, this blog post from Hajan Eskci details what's happening with Web Access:
Team System Web Access in TFS 2010 Beta1
Until now, Team System Web Access was published as an out of band power tool. In this release and beyond, Web Access is now an integrated part of TFS, and it is installed by default when you install TFS.

Deploying ASP.NET 2.0 to IIs7

How to deploy my ASP.NET website to IIS7? I'm using Visual Studio 2005. And I don't know where to start.
I tend to take more of a manual approach, but there is a web publish feature built into Visual Studio that should get you going.
Here is some reading you can do on it:
http://www.codeproject.com/KB/aspnet/VSDeploy.aspx
Here's some preliminary steps, a little more manual than some other options, but they are the ones I'm comfortable with:
Obtain access to the server where IIS7 is installed. If you don't have IIS7 installed on a server, install it. If you are not able to get access to this server, you will need to have the administrator of that server set up IIS7.
Create the website in IIS that you want to deploy to, or have the server administrator create an empty website for you to run your website on.
Use the 'publish' feature in Visual Studio to build a deployable version of your site. This is what you will install on IIS7.
Copy paste the website over to the server where IIS7 is installed. You will need to place it in a directory which you can set as the Home Directory for the site.
If you have access to the server, and rights to administer IIS7, set the Home Directory of the site to point at the directory where you copied over your files.
Enable the website, and you should be good to go!
NOTES:
These instructions assume the following:
a) You have some basic knowledge of how to configure IIS7 (or at least access to somebody who does)
b) You have some basic knowledge of how to install IIS7 if it is not installed (or access to somebody who does)
c) You have some basic knowledge on web site publishing from Visual Studio
If you need more instructions on these 3 notes, you may wish to consult the references for IIS7 and Visual Studio.

Resources