Category: ALM

ALM, SharePoint, TDD2 Comments

New Version of SPEmulators available on nuget

Michael (Mike) Kaufmann

Today I released a new version of the SPEmulators – the package to emulate SharePoint Server API in Farm Solutions – on nuget. The current version is 2.0. The current version includes: Support for Visual Studio 2015 Enterprise Fixed errors for some editions of VS 2012 and 2013 Included Pull Request from Vladimir Almaev with support for SPViewFieldCollection Fixed some minor bugs For installing and using the package please refer to my original post. If you have any questions, issues or feature requests, please create an issue on the project page on GitHub. Continue reading New Version of SPEmulators available on nuget

ALM, O365, SharePoint, TDDLeave a comment

SPOEmulators 0.2-pre released on nuget

Michael (Mike) Kaufmann

I had no support for Visual Studio 2015 in my first beta. I fixed this and added a pester test script to test the init.ps1. I also notices that there are problems with older versions of SharePoint on premises. Therefor I created a second nuget package. The original package SPOEmulators now uses the dependent package Microsoft.SharePointOnline.CSOM as the source for the CSOM assemblies (version 16). The new package SPOEmulators (on-premises) directly references the version 15 of the CSOM assemblies. For details how to use the SPOEmulators refer to the readme on github.com or to my original post here. Continue reading SPOEmulators 0.2-pre released on nuget

ALM, DevOps, O365, SharePoint, TDD2 Comments

SPOEmulators beta available

Michael (Mike) Kaufmann

Today I published the first beta of SPOEmulators on NuGet.org. The project is open source (MIT license) and is available on GitHub. SPOEmulators is a framework that helps you to write unit and integration tests against Office 365 or SharePoint on premise using the client side object model (CSOM). It uses the Microsoft Fakes Framework to emulate the SharePoint or O365 CSOM. The benefit is, that you an write your tests against the real backend as integration tests. If your code works you can add a little more effort to convert the test to an isolated unit test. Like this … Continue reading SPOEmulators beta available

ALM, DevOps1 Comment

New Version of Release Explorer available

Michael (Mike) Kaufmann

There is a new version (2.1 beta) of the Release Explorer for Visual Studio 2013 available. The release explorer is a visual studio extension that allows you to manage your Release Management items from within your Team Explorer in Visual Studio. It is still beta – but the new Version is a lot better than the previous. The current version now allows you to connect to the server using your credentials and you don’t have to save the password in plain text here. This was the biggest pain in the first version for me. In the context menu of a … Continue reading New Version of Release Explorer available

ALM, DevOps, DSC, PowerShellLeave a comment

Don’t forget the NodeName in your DSC ConfigurationData

Michael (Mike) Kaufmann

Today I created a new configuration data for a DSC configuration and got the following error: all elements of AllNodes need to be hashtable and has a property ‘NodeName’. The config looked good: AllNodes was a hashtable and it had the desired node name. So where was the error? I forgot one little thing: the global configuration needs a property NodeName set to an asterisk. Adding this fixed the error. This is really easy – but a search for the error message did not return any useful results. Therefor I decided to share it anyway… Continue reading Don’t forget the NodeName in your DSC ConfigurationData

ALM, DevOps, DSC, PowerShell2 Comments

Be careful with custom variable names in Release Management

Michael (Mike) Kaufmann

If you use Visual Studio Release Management vNext / 2013 with PowerShell/DSC you probably have a lot of custom configuration variables that you pass to your scripts. Be careful when you choose the names for these variables because! There are a lot of reserved words. For example the word UserName is reserved. This leads to very odd error messages that are really hard to track down: System.AggregateException: One or more errors occurred. —> Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException: Permission denied while trying to connect to the target machine <hostname> on the port:5985 via power shell remoting. Please check the following link for instructions: http://go.microsoft.com/fwlink/?LinkID=390236System.Management.Automation.Remoting.PSRemotingTransportException: … Continue reading Be careful with custom variable names in Release Management

ALM, DevOps, PowerShellLeave a comment

Deploy to none domain machines with Visual Studio Release Management vNext

Michael (Mike) Kaufmann

There is a lot of documentation on how to deploy to machines outside your domain using agent based deployment ( i.e. on msdn) using shadow accounts. But I couldn’t find any documentation if and how this is done using vNext / agent-less deployment. If you deploy to server outside your domain you get the following error messge: Connecting to remote server <name> failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.  So this is … Continue reading Deploy to none domain machines with Visual Studio Release Management vNext

ALM, Development, DevOps, O365, SharePointLeave a comment

Side notes for SharePoint and O365 developers from #MSIgnite

Michael (Mike) Kaufmann

I’m not trying to cover all relevant aspects of SharePoint announcements that are made the last days on Microsoft Ignite – I’m sure you’re all following it closely. I just want to highlight the most important aspects for SharePoint developers and the impact they have on my work. Provisioning Engine The Office365 Developer Patterns and Practices group announced a provisioning engine for provisioning SharePoint artifacts (sites, lists, fields, content types etc.). It takes a xml file with a custom syntax as the input and provisions the content using the API. It also works both ways – you can use the … Continue reading Side notes for SharePoint and O365 developers from #MSIgnite

ALM, DevOps, DSC, O365, PowerShell, SharePointLeave a comment

xSharePointProvisioning Module – PowerShell Desired State Configuration (DSC)

Michael (Mike) Kaufmann

The xSharePointProvisioning module contains DSC resources to provision SharePoint artifacts using the Client Side Object Model (CSOM). There are two versions: one for O365 and ne for SharePoint on premise. Currently the following resources are in the package: xList Ensure a list with a specific title and description at a given URL. If the list does not exist it will be created with the specified template. xField Ensure that a list at a specific url has or has not a specified field. XListItem Ensure that a list at a specific url has or has not a list item with the … Continue reading xSharePointProvisioning Module – PowerShell Desired State Configuration (DSC)

ALM, DevOps, DSC, PowerShell1 Comment

Use the DSC Script resource to change the application pool identity

Michael (Mike) Kaufmann

The Desired State Configuration (DSC) module xWebAdministration does not yet support changing the identity of an application pool. There is a community fork cWebAdministration that seems to support it –  but I have not tested it yet. What I did was to use the script resource to change the identity using the module WebAdministration. This is pretty straight forward so I just share the code here. Note that after changing the identity the state of the application pool is stopped. You can use the xWebAppPool resource to start it again. Continue reading Use the DSC Script resource to change the application pool identity