|
Browse by Tags
All Tags » Mono ( RSS)
-
|
SharpDevelop 2.1, as of revision 2135, now allows you to run your unit tests against .NET 1.1 or .NET 2.0. Which framework your tests are run under is determined by the target framework your test project. So if you choose .NET 1.1 as your target framework...
|
-
|
SharpDevelop 2.1, revision 1157, allows VB.NET projects to target the older Microsoft Frameworks and Mono. This extends Daniel 's previous work to target different frameworks with C# . SharpDevelop 2.1 is only available from the repository . To target...
|
-
|
SharpDevelop2 now supports Mono's GAC, so this post takes a low level look into how it uses MSBuild to do this. Our starting point is a previous Custom MSBuild Targets for Mono post, which introduced an MSBuild task (Mcs), which was used to compile the...
|
-
|
In revision 983 SharpDevelop2 has support for Mono's GAC. It also includes new Gtk# and Glade# project templates, and a Gtk# Window file template. Mono can be downloaded from here Creating a new Glade# Project Select the menu option File | New | Solution...
|
-
|
The starting point is the Glade xml file. Glade xml file This was created using the Glade UI Builder that ships with the Mono installer. The xml file specifies the UI components and signals (events) for these components. In our case the main components...
|
-
|
Whilst looking at the NAnt config file (Nant.exe.config), I noticed that NAnt does a much better job at detecting where the Mono compilers, Mcs and Gmcs, are located. NAnt reads the registry, whilst SharpDevelop assumes that they exist somewhere in a...
|
-
|
Targeting Mono with Custom MSBuild Tasks....
|
-
|
SharpDevelop 2.0 now supports Mono 1.1.9.2...
|
|
|
|