I've started migrating my application into the module. The major consideration has been handling the use of LINQ to SQL and the Entity Framework together.
call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\VsDevCmd.bat"
sqlmetal /server:MACHINENAME /database:DBNAME /code:DataContext.cs /language:csharp /views /functions /sprocs /namespace:Models /context:DataBase
- The solution was using a new TransactionScope around the LINQ to SQL calls with TransactionScopeOption.Surpress.
During the development of a module I needed to uninstall the module from the database. There were two options, I used the later.
- I found this tutorial on developing a content part useful. It is detailed and provides another perspective. Yet another useful tutorial in creating a content part is found here. Finally, there is the very basic tutorial on creating a map content part which is perhaps the most useful for its minimalism.
- Turning a content part into a widget is straightforward through the Migration class.
The next step is for me to migrate my Controllers and Views into the module. Part of this is integrating my authentication within Orchard.