Friday, September 9, 2016

command line attach debugger to process

The one liner below will start debugging the IIS processes using Visual Studio. Instead of navigating to the menu using the mouse, Attach Process, check all processes, reverse sort process name, select all w3wp, attach.

(([System.Runtime.InteropServices.Marshal]::GetActiveObject("VisualStudio.DTE")).debugger.localprocesses | Where Name -Match "w3wp.exe").Attach()

This saves time, especially if you need to perform this action several times.

This could also be changed into a function

Function attachdebug

{
param ([Parameter(Mandatory=$true)][ValidateNotNull()]

[String]$Process)

If($process){

(([System.Runtime.InteropServices.Marshal]::GetActiveObject("VisualStudio.DTE")).debugger.localprocesses | Where Name -Match $process).Attach()

}

}

Use:

attachdebug -Process w3wp.exe

Thursday, January 21, 2016

How I solved connection issue in my Hyper-V VM

 

Today I started a VM in Hyper-V. After I logged in to the VM using remote desktop, I noticed that I had no internet connectivity.

To solve this, I just restarted the ICS on the host system.

Below are the PowerShell commands to do so:

get-service sharedaccess | stop-service

get-service sharedaccess | start-service

Now it works fine.

Cheers,

André

Friday, July 20, 2012

Overview of SharePoint Dev training possibilities

 

On the Dev Center of Microsoft is an large amount of online training programs including possibility to do exercises using Virtual Lab or your own VM.

You can find it here.

SharePoint 2013 is also there with 18  modules !!

Wednesday, May 9, 2012

Training kits available at Microsoft

There is large list of training kits available, amongst others containing:

  • SharePoint 2010
  • Office 365
  • Azure
  • Windows Phone

You can find it here

Enjoy!

Thursday, April 12, 2012

Removing a left-over Feature

 

After deactivating and uninstalling a SharePoint 2010 solution, I got an error message.

The result: the solution was removed, but the feature was still there. When I installed and activated the solution again, there were two of features with the same name. So, I could not remove the feature by reinstall/de-install of the solution.

Solution:

I used the Feature Admin Tool to find the left over feature and removed it.

You can find the tool : (Both 2007 and 2010)

http://featureadmin.codeplex.com/

BTW: it is also advised by SharePoint Joel ! and I’ll now add this to my SharePoint tool belt. Smile