.NET Reflector replacement that's free - ILSpy

By -

This is a replacement for .NET Reflector (which has been owned by RedGate since 2011... boooo...)

ILSpy requires the .NET Framework 4.0.

http://ilspy.net/

Comments

Post a Comment

Popular posts from this blog

How to setup Azure Service Bus Relay to use with ACS

By -
In August 2014 Microsoft decided to remove Microsoft Azure Active Directory Access Control (also known as Access Control Service or ACS) from the default Azure Portal setup when creating a new Service Bus Namespace.   Shared Access Signature (SAS) is now default. Service Bus authentication through ACS is managed through a companion “-sb” ACS namespace and to create this we now need to do it from the Azure Power Shell command line (thanks Microsoft!) To do this: Download the PowerShell console https://azure.microsoft.com/en-gb/documentation/articles/powershell-install-configure/#Install Open up the Console and type Add-AzureAccount  and then type in the email address and password associated with your account (Work or Microsoft) Once authenticated you need to create the Service Bus Namespace so it's good to go for ACS. To do this you use the  New-AzureSBNamespace command Parameter Set: Default New-AzureSBNamespace [-Name] <String> [[-Locatio...
Read more

Xamarin Forms - InitializeComponent does not exist in the current context

By -
Image
I was presented with this error whilst developing with Xamarin Forms For me it was simply down to copy and paste :-O.  I'd created a new Xaml Page, which fully qualified was MyNameSpace.MyPage. I then copied in some Xaml which had a different name in the Xaml x:Class attribute (x:Class="NotMyNameSpace.OrPage"). I then tried to compile with our fixing the x:Class attribute and got the 'InitializeComponent does not exist' error. Once I changed the Xaml to match my actual classname (x:Class="MyNameSpace.MyPage") I was back on track and the error went away. Hope this helps. For more information have a look at  forums.xamarin.com The other reason is that you may have created a Shared Xamarin Forms Project rather than a Xamarin Forms Portable project. From Craig Dunn at Xamarin (taken from  Xamarin Forms Forum ) You cannot use Xaml with the Shared Project template with iOS apps (in Xamarin Studio). It's a weird combination to rem...
Read more

Separator Insets on UITableView in iOS8 - Xamarin.iOS

By -
In iOS7 it was possible to configure the separator insets by setting the separator inset property on the tableview: tableView.SeparatorInsets = new UIEdgeInsets(0, 0, 0, 0) In iOS8 this no longer works and you need to set the LayoutMargins on both the table and the cell remembering to check if the property is supported first to avoid breaking iOS7 if   ( this .T ableView . RespondsToSelector ( new   Selector ( " setLayoutMargins : " )))     this .T ableView . LayoutMargins   =   new   UIEdgeInsets ( 0 ,   0 ,   0 ,   0 ) ; Commonly the cell separator insets are set by overriding WillDisplay public   override   void   WillDisplay ( UITableView   tableView ,   UITableViewCell   cell ,   NSIndexPath   indexPath ) {     if   (c ell . RespondsToSelector ( new   Selector ( " setLayoutMargins : " )))         c ell . LayoutMargins   =   n...
Read more