I've just committed a patch to MonoDevelop to enable the use of the AspNetAddIn that I committed a couple of days ago. It's not close to fully-featured yet, but I'm pleased because it now enables a basic ASP.NET workflow. One can create an ASP.NET project and various ASP.NET files, then build and run it. The XSP server will be launched, followed by a web browser, and the compiled page can be seen in all its glory. In theory all .NET languages supported by MonoDevelop can be used, though I have only been able to test C# so far.
There's also some basic CodeBehind support; for example, in the Solution pad, CodeBehind classes are shown as children of the files that inherit them, and the files containing the CodeBehind classes are hidden. This is more powerful than MS's approach, as it allows one file to contain more than one CodeBehind class, or classes that are used for more than one page. But it wouldn't have been possible without MonoDevelop's powerful code parsing services. In addition, when you run the compilation cycle, all page controls with IDs will automatically be added to the CodeBehind class as fields. Don't worry, I plan to make this more granular at some point!
Currently I'm working on integrating the AspNetEdit graphical designer, separating dependencies, and code that could potentially be shared by other designer.
(Update 2006-07-03, 17:43: added screenshot)
Comments
Fantastic work!
Awesome work Michael! I am in the midst of developing an ASP.NET site using monodevelop v0.11 and I am finding the whole
stop apache -> rebuild project -> start apache -> navigate to page
process all a little tedious so am really looking forward to trying this out! If I have time I will download the latest svn tonight and give it a go.
This is great!
Good work, Michael! One question though.. will the project files be compatible with VS.Net? The other developers in my team all use VS.Net but I am keen to switch to MonoDevelop.
Looking forward to trying the designer out.
Unfortunately not
MonoDevelop uses its own project format. However, it is quite possible to maintain parallel MD and VS project files in a project. MonoDevelop does have a VS.NET 2003 importer, but it does not yet support Web Applications.
Just Great!!!
After long time this is best news for me!!!
Keep working on that stuff :o)
what about .NET 2.0 partial classes
i'm not sure about the level of support of Mono on .NET 2.0 stuff, but what about making use of the 2.0 feature partial classes? i'm sure that will make for a cleaner, easier way to do code behinds...
I will use them
I plan to implement support for partial classes when I can be sure that MonoDevelop's parser and code completion can handle them. I have heard that Mono's 1.1 C# compiler can handle them too. Bear in mind that not all of the languages MonoDevelop supports can handle partial classes, so I need to current method as a fallback.
Great news ....
You have earn you pleace in the paradise with all the virgins you want!!! ehehehehh
I only use ASP.NET then if this is ok, I will start to use only the Linux to develop all my projects..... and finally say goodbye to Windows and Virus.
keep the good work
Paulo Aboim Pinto
Odivelas - Portugal
Where is it?
Where is this patch? I don't find it here or the MonoDevelop website.
It's in MonoDevelop SVN
Download MonoDevelop from the Subversion repository, and build it with the option --enable-aspnet.
and debug?
We can debug in the ASP pages and WebControls? Do you intend to implement that too?
tkx
Paulo Aboim Pinto
Odivelas - Portugal
I'd like to implement it eventually
Debugging is something I'd like to support, but there is no way that I can get it done this summer. I will look at it when MonoDevelop's debugging addin is working again.
You are my hero!
I've been waiting for this moment all my life! Now I can switch to Linux completely! You are the greatest!
build failed
When I create a new asp.net project in monodevelop and try to compile I get the following:
Building Solution test
Building Project: test Configuration: Debug
Build failed. null key
Parameter name: key
I can't repro this
I can't reproduce this bug, so unfortunately I can't fix it without more information.
Does this happen with a simple new project, or did you change it at all?
Have you tried a "make distclean; autogen.sh --whatever-options-you-use; make" rebuild?
If you run MonoDevelop from the console, is there any additional trace information when the error occurs?
Problem solved
Appearantly what's causing the trouble is that I have two versions of monodevelop.
I'm using the right one now and the problems are gone.
Here's is my build output:
xsp
Adding applications '/:.'...
Registering application:
Host: any
Port: any
Virtual path: /
Physical path: /home/redman/Projects/Standard/Standard
Listening on port: 8080 (non-secure)
Listening on address: 127.0.0.1
Root directory: /home/redman/Projects/Standard/Standard
But neither firefox or mozilla is launched, I have to launch it manually and then it works.
Is this a bug, or is the code not complete?
Your work is very appreciated and to me, you're like a god,
This is really gonne be the killer application.
Kind regards
Patrick
Are you running Gnome?
Are you running Gnome? By default it should run whichever browser you have set with gnome-default-applications-properties, but I plan to allow a choice of browsers at some point. So it's both a bug, and not complete ;-)
Thanx, gnome-default-applications-properties
I had to change the gnome-default-applications-properties
Yah, It's looking nice...
can I help?
hello
I like C# and Linux so much
so I found Mono Project, and MonoDevelop IDE for Linux, I have some Ideas and I would like to contribute in this project but I don't know where to start
Michael can you give us some advices ????