Tag Info

Hot answers tagged

6

I had the same problem today. I compared the project files with an older version. In my case the Package directory (with the files Package.package and Package.Template.xml) was missing. After copying this directory back from the older version of the project and modifying the csproj file to include the references to the package directory, the error solved ...


4

You need CAS policies when you are not allowed to deploy to the GAC and use other system assemblies. Imagine you have a webpart that reads a log file from disk - you need System.IO from this and thats not allowed in wss_medium (your SharePoint trust level) - in order to say this webpart is allowed to load System.IO you need a CAS policy. If you deploy a ...


4

There is a fine line of difference between IIS Reset and Web Application Pool recycle when it comes to SharePoint Deployments. IIS Reset does 2 important things concerning SharePoint - It recycles all your application pools at one go and clears the memory objects. It reloads all dlls from the GAC(global assembly cache) in the farm servers. Web ...


4

Would this not work? Using the fact that Layouts is shared through the fram targetUrl = '/_layouts/MyProject/AppPage.aspx' + "?Location=" + window.location.href; or you could try: targetUrl = SP.Utilities.Utility.getLayoutsPageUrl('MyProject/AppPage.aspx' + "?Location=" + window.location.href)


3

Looks like you are missing the content type property in your element file, and possibly more: http://blogs.msdn.com/b/bobgerman/archive/2011/01/31/packaging-master-pages-and-page-layouts-with-visual-studio-2010.aspx


3

So, when you reference a dll created in a different project and reference it in your SP project, you need to add it to the Package. To make Visual Studio adding 3rd party assembly or even your own assembly from other project in solution to GAC please do next: Open Package.package from Package folder in SharePoint project. Click Advanced in bottom area. ...


2

There is a related question on SharePoint StackExchange: How to remove orphaned features Remove all the orphaned features: Get-SPFeature | ? { !$_.Scope } | % { $_.Delete() }


2

There is a more fail-safe approach than what @lwbecker2 suggests Get-SPSolution | ? { $_.JobExists } | % { Write-Host "Deployment job is currently running" } This has the benefit of not having a race condition. If you only look for the timer job, it may be that a deployment has already been initiated, but a timer job was not yet created when you check for ...


2

Deploying a wsp on a farm requires the same steps irrespective of the number of WFE servers configured in the farm. In a farm based environment, it is recommended to deploy a WSP via powershell instead of hooking Visual Studio to a WFE server and running a deployment. Visual Studio based deployment should only be done in development systems. If the status ...


2

Your solution has something in it which runs under farm scope, You got two options now, Deploy your solution globally as Robert said or change scope of component scoped as farm. Check this link out for more information as guy is having same problem.


2

We had logic that was calling Install-SPSolution twice on different solutions (same behavior observed with stsadm), and then logic for waiting for the deployment to complete. In rare instances, what happened, is that both solutions were attempting to acquire the deployment lock before either thread got the lock; one thread would succeed and one would fail ...


2

From Development to Staging and Production, always use SharePoint Solution Packages (WSPs) so the SharePoint farm itself takes care of deploying all the artefacts to all the SharePoint servers. Make sure you create WSPs and features to deploy web.config changes as well. Use TFS or any other source control to keep track on all deployments and tie them up to ...


2

That is actually the recommended way of referencing a SharePoint site as it allows for such crazy things as load balancing and even, dare I say, replacing the physical server that runs SharePoint without breaking all of your bookmarks :) Seriously, though. Simply go into Central Administration, System Settings, Configure Alternate Access Mappings, select ...


2

1) yes 2) yes Okay now I have said yes and yes I will explain. In SharePoint you can configure multiple authentication providers, in fact local users will also automatically work out of the box as will AD users because SharePoint uses local accounts itself, (i.e. system account). Therefore any domain or local user made can authenticate. SharePoint is ...


2

there are many factors, some that ill explain! deploying a wsp (solution file) will cause a IISreset, reason being its changing things within the 12/14/15 hive, it could also be adding strongly named dlls to the gac (global assembly cache) and many other factors. IISresets on live servers should NOT be performed during working hours (late evening or ...


2

To your very last question, how to package and deploy solutions of JS files. I would recommend Sandbox solutions. The site collection owner would be able to upload your solution and the solution could deploy the .js and other files to the server. You can update these with a new/updated solution as needed. Be aware that there are some statements about ...


2

Follow the below steps to move workflow into production environment site, In the Development environment open the SharePoint Designer and export the workflow you want using “Export to Visio”. Rename the vwi files by adding ".zip" extension, now open the zip file and remove the "workflow.xoml.wfconfig.xml" because it contains the details about the ...


2

That's a very broad question. data = content like List Items or Documents definitions = content types, site columns, spwebs, spsites, sptimerjobs, workflows when I say "Add" I don't mean you can't change or delete stuff. I'm not sure this list is conclusive or correct, but of the top of my head: SharePoint Hive Farm Solutions Layouts folder ...


1

SharePoint doesn't know which is the Internet, extranet or Intranet zone. When you choose the zone you are telling SharePoint that you will use different behaviour when authenticating users in the Web Application. Each Web Application can have a maximum of 5 zones. The possible zones are: Default Intranet Internet Custom Extranet When you use zones you ...


1

Yes, You have to manually add the custom column on the three environments separately. We too have similar environments and we too do the same process. You make your changes as features and deploy them to each environments using Power Shell or stsadm commands. Since Features support upgrade and you can have versions as well.


1

Do I need to export the site collection and import it in VS2012 (or can I make use of the SP Powershell commands to create the web app & site collection by API)? Use Backup/Restore to move the site collection together with complete structure to your development environment. See more . Remember to deploy your customizations (WSP files) before ...


1

This tutorial will help you: http://tallday.wordpress.com/2010/12/16/developing-sharepoint-2007-webparts-using-visual-studio-2010/ Duplicated here in case the link goes dead: Problem. So i presume your reading this because you love the new Visual Studio 2010 but need to develop web parts for SharePoint 2007. Although the interface within Visual Studio ...


1

Regarding the calendars, this is an annoying bug. SharePoint appears to store the absolute URLs to the calendars. I've come across the same issue when setting up calendars on the site using the internal URL, and then the external users can't use them. Very annoying. Unfortunately, I haven't found a solution other than reconfigure them manually. Might be ...


1

You can back up the development Site Collection by using the SharePoint Central Administration website or Windows PowerShell. Then in your UAT machine, create a SharePoint Application that uses NTL authentication. Then create a new "Team Site Collection" in your UAT SharePoint Application. Then using the backup file, you can restore the Site Collection in ...


1

When deploying Masterpages and Pagelayouts, the feature deploying them should always be SITE scoped as they can only be added to site collection root levels. Then if you want to control which subsites should use the deployed masterpage (if you do not have Publishing Features activated), you create a new feature, which is WEB scoped, with a FeatureReceiver ...


1

Wow. I am surprised someone would say that. My problem has been that there are so many ways of doing custom development for SharePoint 2010. Choosing-the-best-one/where-to-start has been my biggest challenge(s). The four that I have tried (and seen the most) are: Customizing the SharePoint templates (to create a different look/feel) Web Parts (.net) ...


1

Are you sure those features are not set to hidden? Can you perform a new deploy after explicitly specifying Hidden = "FALSE" (hidden attribute equals FALSE by default) in feature manifest? Script usage: Specify the path of your WSPs in the script like C:\wsp_files_location and script will upgrade/install them. $webapplurl = ...


1

Try setting the List attribute to 116 i.e. Master page Gallery. For Master page you don't need a Content type association. Associate your Content Type with relevant page layouts and use fiddler to check the request. See sample below: For master pages: <Module Name="MasterPage" List="116" Url="_catalogs/masterpage" > <File ...


1

Well for a start the "recommended" approach is not to perform testing on your development server. You should have a separate dedicated test environment (and preferably more than one for different types of testing). If you truly want to go the "recommended" approach then you should make sure your entire solution is packaged up as a WSP. This should then be ...


1

A few suggestions: Make sure your solution builds (without deployment) without errors. F6 If not, check that your solution is set to build on Any CPU If not, check that you don't have logical programming errors in your solution When the solution builds: Check your pre- and post- deployment steps ALT + ENTER Still doesn't work? Validate your solution ...



Only top voted, non community-wiki answers of a minimum length are eligible