Search Results

Are you the one that created the web part? Sometimes this can also be a result of the feature trying to reference an object that's not available on the farm (ie: writing to a list that doesn't exist, …

The Visual Studio deployment is designed for development testing. To deploy your feature to production, send over the WSP file and execute the appropriate PowerShell for deployment. …

There isn't out of the box functionality to do this. The only way to prevent bookmarks to individual site pages would be either a full DNS redirection or manipulation of the site in IIS. The former wo …

Personally, I do all of my solution deployment with PowerShell; either create a script or cmdlet to handle multiple scripts, or make something reusable that fits with your internal process. … Actual solution deployment is pretty simple, I tend to come from the school of thought that sometimes us IT folk tend to make things harder than they need to be. …

During the deployment process, the applicable bits for the solution will automatically be "deployed" to any server in the environment with the Foundation Web Application role. … You can then use either Central Administration or PowerShell to perform the "deployment". Once deployed, your feature(s) can be activated, either through the UI, or through PowerShell. …

SharePoint can absolutely do this for you. You should take a look at the MS documentation on the Portal capability: http://sharepoint.microsoft.com/product/capabilities/portals/Pages/default.aspx. I' …

To add another point to what MrChrister and SPUIGuy brought up about the styling and customization end of things. Yes, it's generally considered to be less efficient markup and less standards complian …

Additionally, STSADM is deprecated--you really should move to PowerShell for your deployment tasks. There's a decent overview here of the PowerShell cmdlets vs. STSADM. …