I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals
Related
I need to develop an application for my distributed computing class, with one central server and multiple graphical clients. I was thinking of trying WCF for this, since I am already familiar with making .NET standalone desktop applications using Windows Forms or WPF.
Since I have never worked with WCF before, I am trying to follow a tutorial posted on MSDN, which has defining a service contract as its first major step.* Part of this involves creating a WCF Service Library project, which is supposed to be available as a template under the language of my choice (I am going to use C# here). However, I do not see this project template listed as an option in the new project dialog, and looking for WCF in the search bar returns no results.
How can I make this project template available for use in Visual Studio 2017?
* It should probably be noted that the tutorial mentions that it is written with Visual Studio 2012 in mind. Has anything changed since then that I should be aware of as far as the tutorial is concerned?
Open the installer, choose Individual Components and scroll down to Development Activities. Check the WCF checkbox:
I ended up re-running the Visual Studio Installer to modify my current setup. WCF is not explicitly listed anywhere, but I figured it might have been included as part of the .NET Core or ASP.NET workloads (which were not marked for installation the first time around). After adding these workloads to my installation and restarting Visual Studio 2017, I can now see the WCF project templates listed under C#.
I have the source code of an windows service which is written in VB.NET
I came through various methods to debug this service using development environment (Visual Studio). But the challenge is, I need to deploy it in one of our servers as other application on that server need to access it. The server doesn't contain any development or debug tools. I am not allowed to install visual studio in it.
Is there any other way to debug the windows service on this server?
My intention is to understand the method call hierarchy, as this is a very complex code and I didn't write it. It has a very complex architecture and it is not possible to track the data flow only by looking at it.
If the only restriction is you can't install Visual Studio, I'd suggest you get the Remote Tools for VS 2012, which don't even need to be installed to the server, just a machine with a share accessible from the server. Then follow the instructions.
I'm actually done doing the small-scale application for our office, however, I really don't have any idea how to deploy this one. Can someone provide me any links on how to do this? This project will be deployed in one pc.
If its a Windows application you need to create a setup project.
If its a web based application, install your application on your web server and provide clients with the appropriate link.
I have to modify an ASP.NET Web Forms application which is currently on production on a Windows Server 2003 in II6.
The problem is that I didn't develop the application and there is not anymore the Visual Studio solution used to develop the application. Moreover the application lies under a website where other applications are running and the connection strings are stored in the global web config file.
I want to modify the application without compromising the version that is actually online.
How can I bring the production version back into a solution file? Many thanks
Is there anyway to develop sharepoint projects without having sharepoint server installed locally. I have a sharepoint server running at my work and vs2010 installed locally. I want to be able to test my projects on the server.
You develop them locally but without SharePoint installed you cant test them. Microsoft Offers no free version of SharePoint Server, so you have to be able to use a licensed copy of SharePoint to test on it. I just use a Remote Desktop Connection to connect to my DEV machine that has SP installed on and Visual Studio. I then develop my app then test, and then it gets deployed to our SharePoint Farm.
Yes, it is possible. You just need to build wsp and then deploy it on a SharePoint server. I hope, this links will help you:
Creating a SharePoint Solution Package (.wsp) in 5 steps
WSPBuilder (SharePoint WSP tool)
Installation and Deployment of a Farm Solution in SharePoint 2010