SharePoint 2010: RemoteStsAdm PowerShell Module is available via NuGet | Ideas For Free - Dec 0, 2011
[…] PowerShell: Introducing Import-PSModule […] Steve B. - Apr 4, 2012
Very promising. I’m wondering if the nuget repository could be a file share, like it should be possible within VS… thx for your great job [cakriwut]( “cakriwut@gmail.com”) - Apr 5, 2012
Hello,
Yes, it is possible to use file share for nuget repository.
You may already know PsGet by Chaliy or PsGet by Anurse for PowerShell module distribution. They have created PowerShell module distribution mechanism with different approach.
Chaliy uses PowerShell script approach and customized module directory. Everytime you want to distribute your PowerShell module, you have to fork his github project to update Directory.xml content. Even tough the instruction in https://github.com/chaliy/psget/wiki/How-to-add-your-module-to-the-directory is very clear, however I think there is risk of incorrect Directory.
SharePoint 2010 : RemoteStsAdm PowerShell Module | Ideas For … | Mastering Sharepoint - Sep 6, 2011
[…] the original post here: SharePoint 2010 : RemoteStsAdm PowerShell Module | Ideas For … ← SharePoint 2010 Development with Visual Studio 2010 (Microsoft […] SharePoint 2010: RemoteStsAdm PowerShell Module is available via NuGet | Ideas For Free - Dec 0, 2011
[…] Few month ago I have introduced RemoteStsAdm, a PowerShell module that enable you to execute StsAdm.
English
The STSADM.exe is command-line tool for administration of Office SharePoint Server (SharePoint 2007, SharePoint 2010). It is installed on the same location as SharePoint Products and Technologies location: %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin (for SharePoint 2007) or %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin (for SharePoint 2010). You must be Farm Administrator to be able to run the tool.
By default, the STSADM.exe must be executed locally since it will access SharePoint Object Model.
English Either you’re SharePoint geeks or newbie, intellisense is always helpfull to provide inline guidance. Previously we need to configure Visual Studio environment manually to get very basic information about CAML schema. After all, we always need better and better tools for the job. Thanks to John F. Holliday , that provides free Visual Studio 2010 add-ins for more sophisticated CAML intellisense - the CAML.Net.Intellisense. You can download the bits in Visual Studio Gallery ( Gallery > Tools > caml.
English SharePoint team just released SharePoint 2010 Administration Toolkit V1, which contains : - User Profile Replication Engine 2010 - Security Configuration Manifest - Content Management Interoperatibility Services Connector - Load Testing Kit More information about this toolkit can be found here: http://blogs.msdn.com/b/sharepoint/archive/2010/07/15/announcing-the-release-of-the-sharepoint-2010-administration-toolkit-v1.aspx
English I am trying to blog howto series on administration with graphical descriptions. 1. Howto configure personal regional settings. 2. Howto limits page layouts availability in web site. 3. Howto enable debuging in SharePoint Web Application. 4. Howto configure alternate access mapping. 5. Howto remove My Site or My Links link. … and more are coming.
Elcorin - Sep 2, 2009
Hi, Thank you! I would now go on this blog every day! Elcorin Cristi Faycurry - Oct 5, 2010
The formal post assited me a lot! Saved the website, extremely great topics just about everywhere that I read here! I like the information, thank you.
English
Today, I almost missed an update of very nice tool – Microsoft SharePoint Administration Toolkit. I browse to Microsoft SharePoint Team Blog, – found out that they already announce the 4th release last week.
But before you can play around with the tools, you will need to install following pre-requisites:
Service Pack 2 for WSS and SharePoint Server 2007 April Cumulative Update for WSS and SharePoint 2007. The April CU comes as hotfix – so you will need to register your email address and get the download link + password from your inbox.
English
Remember about critics to “stsadm –o copyappbincontent” to deploy SharePoint resource in my previous post here.
At the end of the post, I think that it should be “stsadm –o copyfarmappbincontent” instead.
Why?
Because the last will work in centralized deployment mode, same as solution deployment.
But what’s the secret? Why the standard copyappbincontent doesn’t work in farm configuration?
I’ll post in another article. But now, I have created the project in Codeplex.