I can't find any information on why this might be a problem.  The only thing I can think of is that m_instance is a static (shared) variable.  So maybe you have to access it that way even though you are in a static (shared) method.  Did you try doing something like "Facade.m_instance ="?

That's really the only thing that comes to mind....

The code for the instance method in c# looks like this, so you need to do something similar in VB.

:


/// <summary>
/// Facade Singleton Factory method.  This method is thread safe.
/// </summary>
public new static IFacade Instance
{
get
{
if (m_instance == null)
{
lock (m_staticSyncRoot)
{
if (m_instance == null) m_instance = new ApplicationFacade();
}
}

return m_instance;
}
}


I will take a look and see what I can figure out later on tonight....

Hi Peter,

Sorry for the slow response.  The way I instantiate PureMVC in my WinForms apps is in the following way:

:

/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main(string[] args)
{
try
{
Application.SetCompatibleTextRenderingDefault(false);
MainForm mf = new MainForm(args);
ApplicationFacade facade = (ApplicationFacade) ApplicationFacade.Instance;
facade.Startup(mf);
Application.Run(mf);
}
catch (Exception ex)
{
// Log some errors, show message box, etc.
}
}

I hope this helps some, and post any other questions you have.

Andy Adamczak

Yes, this looks like a bug.  I will fix it and check it in.  I have uninstalled Visual Studio 2005 from my development machines, since it's 2 revisions back, but I should be able to recompile all the dlls.

That's the first bug found in my multi-threaded implementation!

I have not seen any major PureMVC Silverlight applications.  I, personally, have written some significant C# winforms applications using PureMVC, and PureMVC has been extremely effective in those applications.

If you actually compare the sources of the ActionScript Proxy and C# Proxy, the code for the static NAME variable and the constructors are almost exactly the same (the three constructor overload correspond to the default values allowed in the ActionScript constructor).  The way to typically use a name on the proxy, is that you create a "public new const string NAME" on your subclass with a class specific value, and you use that NAME variable to retrieve or remove proxies.  This is the same usage pattern used in the ActionScript implementation.

Andy

I wanted to post a startup idiom for WPF applications.  There is a timing issue on when the main window is available for the application facade startup.  The way I found that works great is to override your OnStartup event of you application in your App.xaml.cs file (this is the default file name generated by Visual Studio), and instantiate your main window by hand.  This is the suggested method of doing things if you need access to your main window in the startup event.  So first, you have to remove the StartupUri attribute from your App.xaml source.  Then you override your OnStartup event so it looks something like this:

:

protected override void OnStartup(StartupEventArgs e)
{
base.OnStartup(e);
MainWindow window = new MainWindow();
ApplicationFacade facade = (ApplicationFacade) ApplicationFacade.Instance;
facade.Startup(window);
window.Show();
}


Sorry for the slow response on this.  Anyway...

I actually haven't had any experience with asp.net and using PureMVC.  I currently have used it for several Forms application and a WPF application.  I've also done a little bit in Silverlight, but just enough so I can get a library build done and tested.

I've seen talk about PureMVC being used in asp.net apps, mapping the view / mediator part of PureMVC to the aspx pages, and commands to the middle tier and the model to the data tier.  I just haven't seen any concrete examples for it.

Andy

I just checked in the project changes, so by default the generated dlls are not signed.

I will check in the solutions so that they are not signing the dlls.  The dlls that are checked into svn will be signed though.