SharpDevelop

Given the all-time high of forum spam we are encountering, we decided to switch new user's to being moderated. Thus, your initial post will show up only after it has been reviewed by one of the team members assigned the moderator role. Once your post ... [More] is verified, your account's moderation requirement will be lifted. Our team does its best to release your posts in a timely manner, but given that we do not span all time zones, it sometimes might take a few hours for your post to be approved. Thank you for your understanding. [Less]

SharpDevelop 4.4 now has support for Code First Migrations using Entity Framework 6.0.2. On NuGet there is an EntityFramework.SharpDevelop NuGet package that includes the original Entity Framework assemblies along with custom versions of the ... [More] PowerShell cmdlets, listed below, that work with SharpDevelop Enable-Migrations: Adds support for migrations to your project. Add-Migration: Generates code for a database migration based on changes to your database model. Update-Database: Applies migrations to the database. Get-Migrations: Shows the migrations that have been applied to the database. Now let us take a look at how to use the EntityFramework.SharpDevelop NuGet package. Installation Before you begin you should have SQL Express installed. You will also need SharpDevelop version 4.4.0.9722 or above. We will look at using Entity Framework in a simple C# console application. This application will add a blog post to a SQL Express database and then read all the existing blog posts in the database. We used this example before in a previous blog post when using Entity Framework with SharpDevelop so we will not go into as much detail as before, instead concentrating on some of the new features that Entity Framework brings, such as logging and support for stored procedures. In SharpDevelop first create a new C# Console Application. Add the EntityFramework.SharpDevelop NuGet package to the project either by using the Manage Packages dialog or by using the Package Management Console window. Using Entity Framework Here is the code we will start with. using System; using System.Data.Entity; using System.Linq; namespace EFCodeFirst { public class Post { public int Id { get; set; } public string Title { get; set; } public string Text { get; set; } } public class BloggingContext : DbContext { public DbSet<Post> Posts { get; set; } } class Program { public static void Main(string[] args) { Console.Write("Enter a post title: "); string title = Console.ReadLine(); Console.Write("Enter the post text: "); string text = Console.ReadLine(); using (var db = new BloggingContext()) { db.Database.Log = Console.Write; var newPost = new Post { Title = title, Text = text }; db.Posts.Add(newPost); db.SaveChanges(); Console.WriteLine("All posts in the database:"); IQueryable<Post> query = db.Posts .OrderBy(p => p.Title) .Select(p => p); foreach (Post post in query) { Console.WriteLine("Post.Title: " + post.Title); } } Console.WriteLine("Press a key to exit."); Console.ReadKey(); } } } The above code uses the new logging feature of Entity Framework 6. The line after the database context is created configures Entity Framework to write information, such as the queries executed, to the console: db.Database.Log = Console.Write; Running the console application will cause Entity Framework to create a new database, add a new post to the database, and then read all the posts from the database. You will also see information logged by Entity Framework: INSERT [dbo].[Posts]([Title], [Text]) VALUES (@0, @1) SELECT [Id] FROM [dbo].[Posts] WHERE @@ROWCOUNT > 0 AND [Id] = scope_identity() -- @0: 'first' (Type = String, Size = -1) -- @1: 'first post' (Type = String, Size = -1) -- Executing at 21/12/2013 12:09:06 +00:00 -- Completed in 11 ms with result: SqlDataReader All posts in the database: SELECT [Extent1].[Id] AS [Id], [Extent1].[Title] AS [Title], [Extent1].[Text] AS [Text] FROM [dbo].[Posts] AS [Extent1] ORDER BY [Extent1].[Title] ASC -- Executing at 23/12/2013 12:09:06 +00:00 -- Completed in 2 ms with result: SqlDataReader Database Migrations Now let us take a look at adding a new migration. Open the Package Management Console and run the following command to configure database migrations for the project. Enable-Migrations We will now use the new stored procedure support that was added to Entity Framework 6. Instead of inserting, updating and deleting posts in the database using SQL we will use stored procedures. To do this we modify the database context as shown below. public class BloggingContext : DbContext { public DbSet<Post> Posts { get; set; } protected override void OnModelCreating(DbModelBuilder modelBuilder) { modelBuilder .Entity<Post>() .MapToStoredProcedures(); } } Here we have overridden the OnModelCreating method and configured Entity Framework to use stored procedures for our Posts. Now generate a code first migration for the stored procedures by running the following command in the Package Management Console. Add-Migration StoredProcs This creates a new migration that includes a set of simple stored procedures for inserting, updating and deleting Posts in our database. Part of this generated code is shown below: public partial class StoredProcs : DbMigration { public override void Up() { CreateStoredProcedure( "dbo.Post_Insert", p => new { Title = p.String(), Text = p.String(), }, body: @"INSERT [dbo].[Posts]([Title], [Text]) VALUES (@Title, @Text) DECLARE @Id int SELECT @Id = [Id] FROM [dbo].[Posts] WHERE @@ROWCOUNT > 0 AND [Id] = scope_identity() SELECT t0.[Id] FROM [dbo].[Posts] AS t0 WHERE @@ROWCOUNT > 0 AND t0.[Id] = @Id" ); Now you can add the new stored procedures to your database by running the following command in the Package Management Console window. Update-Database The stored procedures can be seen using SQL Management Studio. If you run the console application now you will see the stored procedures being used when a new post is created in the console output. [dbo].[Post_Insert] -- Title: 'second' (Type = String, Size = 1073741823) -- Text: 'second post' (Type = String, Size = 1073741823) -- Executing at 23/12/2013 12:21:47 +00:00 -- Completed in 5 ms with result: SqlDataReader That concludes our look at using Entity Framework 6 code first migrations with SharpDevelop. Further Information on Entity Framework Entity Framework on the MSDN. Entity Framework 6: Database Access Anywhere, Easily - Rowan Miller's Tech Ed 2013 Talk. The code for the modified NuGet packages is available on GitHub. [Less]

Fody is a NuGet addin, written by Simon Cropp, that will weave IL instructions into your assembly after it has been compiled. IL weaving is the creation and manipulation of IL without the use of a compiler. To do the IL weaving Fody uses a MSBuild ... [More] task and Mono.Cecil. Fody is a general purpose IL weaver and is extended using Fody addins, which are also NuGet packages. One example is the PropertyChanged addin which will inject INotifyPropertyChanged code for your class properties into your assembly without you having to write the code. Another example is the NullGuard addin which will add null checks to your code. For the full list of Fody addins see the list on the Fody GitHub page: Now let us take a look at using the NullGuard addin with SharpDevelop. You will need to use the latest version of SharpDevelop 4.4. Any version from 4.4.0.9711 or above should work. Previous versions of SharpDevelop would not correctly configure the path to the Fody assembly which would cause the project to fail to compile. Installing Fody Fody is a NuGet package so use either the Manage Packages dialog or the Package Management console to install the Fody nuget package into your project. Installing the Fody NuGet package will add a FodyWeavers.xml and a Fody.targets file to your project. The FodyWeavers.xml file configures the Fody addins that will be used. The project itself will be updated so it imports the Fody.targets file which is a custom MSBuild targets file. Also a FodyPath property will be added to your project so the Fody.dll assembly can be located and used by the Fody MSBuild targets file. Installing NullGuard addin Search for the NullGuard.Fody in the Manage Packages dialog or use the Package Management Console and install it. Installing the NullGuard.Fody NuGet package will update the FodyWeavers.xml file so the NullGuard addin will be used by Fody. <?xml version="1.0" encoding="utf-8"?> <Weavers> <NullGuard /> </Weavers> NullGuard Generated Code Now let us take a look at what code is generated by Fody and the NullGuard addin when the following class is included in the project: using System; namespace NullGuardTest { public class MyClass { public void MyMethod(string parameter) { } } } Compiling the project will now weave in null checks into your assembly. If you open your assembly into ILSpy you can view the generated code, which is shown below: using System; using System.Diagnostics; namespace NullGuardTest { public class MyClass { public void MyMethod(string parameter) { Debug.Assert(parameter != null, "[NullGuard] parameter is null."); if (parameter == null) { throw new ArgumentNullException("parameter", "[NullGuard] parameter is null."); } } } } The NullGuard addin has added null checks for the parameter being passed into the method without you having to write the code yourself. The generated assembly IL can be further controlled by adding attributes to your class. Further information on the supported attributes that are available can be found on the NullGuard GitHub page. That is the end of the quick introduction to using Fody with SharpDevelop. [Less]

Many of SharpDevelop's features light up only if you install certain dependencies. So far, we only had them listed on the downloads page, which you might have already closed once you start the installer. That's why we decided to more prominently ... [More] "advertise" those - SharpDevelop 4.4's setup sports a new Finished page which encourages you to learn about dependencies right when you need them: It is not a classic readme but really a list of recommended (freely downloadable) software that you should consider installing. Currently, the list looks like this: Depending on your needs, feel free to mix & match. (but make sure to install the first one!)   [Less]

Simply take a look at the following comparison screenshot: SharpDevelop 4.4 now supports displaying documentation for the recent .NET framework 4.5 and 4.5.1 upgrades in code completion. You can get the Developer Pack from here. SharpDevelop 4.4 ... [More] nightly builds are available here. Enjoy! NOTE: These changes are not yet merged into SharpDevelop 5.0. (Read: SharpDevelop 5.0 doesn't yet support the documentation for .NET 4.5 and 4.5.1.) [Less]

  A new feature in SharpDevelop 4.3.3 is the ability to define a template icon that will be loaded from the file system. Until SharpDevelop 4.3.2 only icons from the SharpDevelop resources could be used as template icons. Now you have the ... [More] possibility to display your own template icon placed in the file system just by using the prefix file: like that: The placeholder ${SharpDevelopBinPath} is replaced by the path where the SharpDevelop binaries are located. Another placeholder you can use is the placeholder for an Add-In path by using ${AddInPath:<NameOfAddIn>}. This placeholder is replaced by the path where the named Add-In is located. An Example would be ${AddInPath:ICSharpCode.FiletypeRegisterer}. If the icon exists in the defined path (see declaration in the first screenshot) it will be displayed in the "New Project" dialog: Enjoy this new feature and happy templating! [Less]

SharpDevelop 4.3.3 has been updated to use NuGet 2.7 and now has support for restoring NuGet packages. Restoring NuGet Packages To restore NuGet packages for your solution, from the Projects window right click the solution, project or References ... [More] , and select Restore NuGet Packages. This will run NuGet.exe and uses the new restore argument that has been added to NuGet 2.7. The full command line will be similar to the following: NuGet.exe restore YourSolution.sln The output from this command will be shown in the Output window. In the screenshot below you can see jQuery, Json.NET, Modernizr and NUnit being restored. [Less]

Especially when working with XAML files and C# code-behind files, I found it annoying that SharpDevelop always landed me in the XAML part of a class when Ctrl+clicking on the type name of a window or control. Now SharpDevelop will display a popup when there are more parts you could want to jump to:

Sometimes it is useful to only see search results from specific projects. It makes it easier to refactor only a part of a solution without having to pay attention to not edit files in the wrong projects. Hence I implemented two new grouping modes in ... [More] the search results pad: Group by project: Group by project and file creates two levels of tree nodes: [Less]

Noam Wies contributed a feature to Ctrl+G searching: you need to only specify the capital letters of the parts, and it will find types / files like the normal Ctrl+G search. Example: instead of searching for 'CSharpP' you search for 'csp' and it ... [More] will find CSharpParser, CSharpParameterCompletionEngine et cetera. This will be part of the SharpDevelop 4.3.2 release. [Less]