After digging around a bit and virtual gumshoeing, I was finally able to get my MM 1.1.3 web based app working under MM 1.2.

FYI & FWIW, I ran into three problems. Here they are along with the fixes:

PROBLEM 1:

After upgrading, I opened a Permit solution I had built earlier with MM.NET 1.1.3 When I tried to open the file Business.cs to add some new stuff in there, I got an error:

***
The base class 'OakLeaf.MM.Main.Business.mmBusinessObject' cannot be designed.
***


SOLUTION (thanks to Chris McCandless for this one!):

- Open BusinessObject with RightClick+View Code ( simply double clicking the BusinessObject WILL give the error)
- Change ABusinessObject class definition from
public class ABusinessObject : mmBusinessObject
to
public class ABusinessObject : OakLeaf.MM.Main.Business.mmBusinessObject

- Save the change
- Open the class again (NOW you can double click it...)
- Change ABusinessObject class definition BACK to
public class ABusinessObject : mmBusinessObject
(You actually HAVE to change it back to avoid a compiler error...)
- Save the change

And now all was well with this one.



PROBLEM 2:

When trying to run the application, I get this error next:

***
Prepared statement '(@UserFK nvarchar(4000)) SET FMTONLY OFF; SET NO_BROWSETABLE ON;' expects parameter @UserFK, which was not supplied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Prepared statement '(@UserFK nvarchar(4000)) SET FMTONLY OFF; SET NO_BROWSETABLE ON;' expects parameter @UserFK, which was not supplied.
***

SOLUTION:

After messing around with this, I found that temporarily setting EnableSecurity = true in the LOGIN page cleared THIS problem. I may also have set EnableSecurity to false, compiled, and then set it back to true again on my main form, which is supposed to kick up the login form. I have NO idea why this worked, but it did. Good enough for me...


PROBLEM 3:

Value cannot be null. Parameter name: String
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: String

Source Error:


Line 40: //
Line 41: InitializeComponent();
Line 42: base.OnInit(e);
Line 43: }
Line 44:


Source File: C:\Inetpub\wwwroot\Wait Net Web Application\UserLogin.aspx.cs Line: 42


SOLUTION:

After messing around and experimenting with THIS problem for a while, I decided to try setting the add key="LocalizeApp" value="true" and add key="DefaultLanguage" value="1" in the web.config file, even though this app does NOT need to be localized.

It STILL didn't work, but this time I was able to figure out the necessary additional localization steps from the MM.NET 1.2 help file. I ran the SQL script to create the Language table. I also found out that since my application is accessing two different databases, I had to set add key="MessageDatabaseKey" value="Northwind" (I created the Language -table in the Northwind database)

It STILL didn't work, giving me access errors on Language -table. This time I remembered to open the Language table with SQL Server Enterprise Manager and set proper permissions for ASPNET apps.

It STILL didn't work, giving me access errors on the Message -table. I set up proper permissions for ASPNET apps for this table, too.

Then I pressed the F5 -key on the .NET IDE and held my breath..........

And, voila! NOW my application opened up just like it did with version 1.1.3! I was back to where I started, albeit on a higher framework revision.

[And don't I EVER learn to NOT jump on any new software releases (my OWN included <s>...)? I guess not. Any self respecting shrink would probably tell me (for $150.00 or more) that I'm a glutton for punishment and a masochist to boot for doing these bleeding edge things to myself <g>.]

Hopefully other MM.NET upgraders out there will find this yarn useful and save $150.00 and a few hours of hair-pulling.

And by the way, I'm not trying to bash MM.NET here. IMHO it really is a very useful product, and I am sure that it will be even much more useful after a few more revs. I just hope that those future upgrades shall be much less of a pain in the old keester than I found this one to be.


Cheers,

Pertti