[Mono-list] 1.0 Release and Developing in VS.net (VB)
Will the 1.0 release support DLL's built with VB in VS.net? If so will there be any support or documentation on how to do this with the release? I assume this would mean no client side script blocks in VB.net... Thanks for clarification. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Expected 1st Novell Suse release?
Is there an expected 1st release of Suse by Novell? Will mono be shipping with it? ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] asp.net or php
True object oriented language whereas php is more like original asp. -Original Message- From: Alejandro Sánchez [mailto:[EMAIL PROTECTED] Sent: Sunday, January 18, 2004 8:49 AM To: [EMAIL PROTECTED] Subject: [Mono-list] asp.net or php what are the advantages of asp.net over php? -- Alejandro Sánchez e-mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] DotNetNuke, VB.Net and mono
The next version of DNN will sport a new DAL and BLL that will make it database agnostic (assuming there exists or you write a dataprovider for it). This is really very slick and the providers will run as private assemblies: http://www.dotnetnuke.com/admin/Portal/LinkClick.aspx?tabid=478&table=Documents&field=ItemID&id=34&link=DotNetNuke+Data+Access.doc I do believe there were some folks trying to make this run on mono but I am very interested in this answer as well. -Original Message- From: Jeff Kowalczyk [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 9:55 AM To: [EMAIL PROTECTED] Subject: [Mono-list] DotNetNuke, VB.Net and mono I've deployed the DotNetNuke portal in recent months, and the users have been extremely pleased. DNN is an enhanced rewrite of IBuySpy ASP.Net portal, unfortunately derived from the VB.NET version instead of C#. There is an active market in useful third party components, which makes a transition to C# unlikely for the DNN community. Some third party components are available only as compiled private assemblies, but fortunately source is available for DNN and most third party components. For all its utility and favor with my users, DNN is unfortunately tying me to running at least one Windows/SQL server for the foreseeable future. Other than DNN, I have everything running on Linux. What are the prospects for either: a) mono's VB.NET compiler coming up to the point where it can compile a comprehensive ASP.Net app like DNN, or b) running the windows-compiled DNN and third party components on mono irrespective of the source language? I know this should work, but does it in practice? Also, have any of the postgres/mysql provider projects implemented anything that would help .Net apps that presume SQL server to work with alternative databases using impersonated library names? Obviously there would be issues with SQL differences, etc. Thanks. Links: http://dotnetnuke.com note: Mozilla users may have trouble with the tab navigation javascript at the top of DNN portals, this is being fixed in 2.0 http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=412399 ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Novell, SuSE, Mono.
So when will we see the first Novell / Suse release? Will it be far off? -Original Message- From: Olaf Jan Schmidt [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 5:50 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Mono-list] Novell, SuSE, Mono. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Miguel, hi Mono and KDE folks! [Miguel de Icaza] > Hey guys, > >I know that there has been a lot of speculation over Novell, SuSE, > Gnome, KDE and Mono with today's announcement. > >We can say that once the acquisition is completed that: > >* Novell/SuSE will continue to distribute KDE and Gnome. > >* Novell/SuSE will include Ximian Desktop build, > as it is a more fine tuned desktop than the default Gnome > build they ship. > >* Novell is commited to build an stable ISV platform (you can > read my blog for some thoughts on this). > >* Gtk+, the Gnome platform and Mono use the right licensing > terms for creating an ISV platform. > >* We will continue to work on open source projects, and work > in the best way to offer a complete Linux stack. > >And lastly, just remember that Nat and myself are in charge of > Novell's Linux Desktop Strategy, so we will do the right thing ;-) Does the "right thing" include better cooperation between KDE and Mono/GNOME, meaning contributions to ALL these projects with at least the same efford as in the past? Or will SuSE's currently big support for KDE be phased out after carefully examining how quickly it can be dropped without alienating the developer community? Or does it also depend on what the SuSE people think is best for their customers? I am a bit worried by the fact that you only spoke of "distributing" KDE, not of actively supporting it. Not saying something sometimes says the most. KDE and GNOME are both so important for the Linux desktop that dropping contributions to one of them would be very sad. I see great possibilities in the cooperation between Ximian and SuSE for free desktop interoperation - which is urgently needed for accessibility, the area of KDE I am involved in. I hope my hopes are not too optimistic. > > Love, > Miguel. Love and peace, Olaf > ___ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list - -- Olaf Jan Schmidt, KDE Accessibility Project KDEAP co-maintainer, maintainer of http://accessibility.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj+pfpIACgkQoLYC8AehV8cU6gCg58qcRy7VLDU0BMMjLOZPSU2y XmcAoK3JTE6wiyoWz91PqsP43Jc0pwWP =9aof -END PGP SIGNATURE- ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Running MS compiled ASP.NET in Mono.
How does this work with vb.net pre-compiled dlls? -Original Message- From: Gonzalo Paniagua Javier [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 1:50 PM To: [EMAIL PROTECTED] Subject: Re: [Mono-list] Running MS compiled ASP.NET in Mono. El lun, 29-09-2003 a las 18:53, Mark Furniss escribió: > Hi, > > We have successfully installed Mono / XSP and mod_mono. The example > files supplied all run fine and also any simple (inline C#) ASPX files I > create are fine, however when I attempt to run any of our ASP.NET > applications (written in MS Visual Studio using compiled aspx.cs files) > they fail (see example error below this post). > > Can anyone tell me if it is possible to just copy over a compiled MS > project that uses "code behind modules" and then run it, or do I need to > compile it using MCS.exe on Linux? > > Basically I am looking to develop on Windows and deploy on Linux. > > Assuming this is possible can anyone tell me if they are using > Mono/mod_mono (apache) in a production environment? > > Many thanks > Mark. > > > Parser Error > Description: Error parsing a resource required to service this request. > Review your source file and modify it to fix this error. > > Error message: Cannot find type HelloWorld._Default > > File name: /home/markf/xsp-0.5/server/test/HelloWorld/Default.aspx > Line: 1 > > Source Error: > > <%@ Page language="c#" Codebehind="Default.aspx.cs" > AutoEventWireup="false" Inherits="HelloWorld._Default" %> > > > Visual Studio should compile Default.aspx.cs into a dll and that dll should be in 'bin' directory. If you copy those dlls in bin to linux, it should work. -Gonzalo ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Running MS compiled ASP.NET in Mono.
So is there clear error reporting as to what is not implemented if the assemblies do not execute because you have code that calls methods that are not completed? -Original Message- From: Gonzalo Paniagua Javier [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 1:50 PM To: [EMAIL PROTECTED] Subject: Re: [Mono-list] Running MS compiled ASP.NET in Mono. El lun, 29-09-2003 a las 18:53, Mark Furniss escribió: > Hi, > > We have successfully installed Mono / XSP and mod_mono. The example > files supplied all run fine and also any simple (inline C#) ASPX files I > create are fine, however when I attempt to run any of our ASP.NET > applications (written in MS Visual Studio using compiled aspx.cs files) > they fail (see example error below this post). > > Can anyone tell me if it is possible to just copy over a compiled MS > project that uses "code behind modules" and then run it, or do I need to > compile it using MCS.exe on Linux? > > Basically I am looking to develop on Windows and deploy on Linux. > > Assuming this is possible can anyone tell me if they are using > Mono/mod_mono (apache) in a production environment? > > Many thanks > Mark. > > > Parser Error > Description: Error parsing a resource required to service this request. > Review your source file and modify it to fix this error. > > Error message: Cannot find type HelloWorld._Default > > File name: /home/markf/xsp-0.5/server/test/HelloWorld/Default.aspx > Line: 1 > > Source Error: > > <%@ Page language="c#" Codebehind="Default.aspx.cs" > AutoEventWireup="false" Inherits="HelloWorld._Default" %> > > > Visual Studio should compile Default.aspx.cs into a dll and that dll should be in 'bin' directory. If you copy those dlls in bin to linux, it should work. -Gonzalo ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
