ASP.NET MVC + Mono + Linux
Posted: Wed 15 Dec 2010 05:29
This licensing issue has me so confused and I'd really like to solve it because otherwise it seems like yours is a great solution.
I want to deploy an ASP.NET MVC application on Linux (Ubuntu and/or CentOS) using Mono 2.6.7. The application itself will not contain the DotConnect LINQ code; this will be in a separate assembly. Let's call the app MyMvcApp and the dll MyMvcApp.Data.dll
So:
1. Do I need to embed the license code in just MyMvcApp.Data.dll, in just the ASP.NET MVC app, or both somehow?
2. If the app, how exactly do I do this? I do have access to Visual Studio to perform the compilation.
3. Do I need to compile the license file every time the DLL and/or MVC app changes, or can I compile it once on Windows then add it as a resource each time I compile on Linux? I'd prefer to *not* need Visual Studio for my regular development.
PLEASE, please don't just say that it's explained in detail in http://www.devart.com/dotconnect/mysql/ ... ml#compile because that doesn't reference ASP.NET MVC anywhere and it isn't at all clear whether I can compile the license once on Windows or have to compile it each time the code changes. I guess "Class Libraries Support" explains it a bit but an ASP.NET MVC site doesn't create an .exe so I don't know what to put in licenses.config.
And can I just say that all of this is extremely confusing and frustrating, yes I know it's "the standard Microsoft .NET licensing tool" but you have a great solution to a cross-platform problem here and I'd really LOVE to give you my money but this awkward manual process is just terrible. Please come up with a fully-managed way to control your licenses so that Mono/Linux users don't have to deal with this!! I really hope you're not going to say I have to compile in VS every time because that will probably cause me to look elsewhere
I want to deploy an ASP.NET MVC application on Linux (Ubuntu and/or CentOS) using Mono 2.6.7. The application itself will not contain the DotConnect LINQ code; this will be in a separate assembly. Let's call the app MyMvcApp and the dll MyMvcApp.Data.dll
So:
1. Do I need to embed the license code in just MyMvcApp.Data.dll, in just the ASP.NET MVC app, or both somehow?
2. If the app, how exactly do I do this? I do have access to Visual Studio to perform the compilation.
3. Do I need to compile the license file every time the DLL and/or MVC app changes, or can I compile it once on Windows then add it as a resource each time I compile on Linux? I'd prefer to *not* need Visual Studio for my regular development.
PLEASE, please don't just say that it's explained in detail in http://www.devart.com/dotconnect/mysql/ ... ml#compile because that doesn't reference ASP.NET MVC anywhere and it isn't at all clear whether I can compile the license once on Windows or have to compile it each time the code changes. I guess "Class Libraries Support" explains it a bit but an ASP.NET MVC site doesn't create an .exe so I don't know what to put in licenses.config.
And can I just say that all of this is extremely confusing and frustrating, yes I know it's "the standard Microsoft .NET licensing tool" but you have a great solution to a cross-platform problem here and I'd really LOVE to give you my money but this awkward manual process is just terrible. Please come up with a fully-managed way to control your licenses so that Mono/Linux users don't have to deal with this!! I really hope you're not going to say I have to compile in VS every time because that will probably cause me to look elsewhere
