Is the error preventing the application from working? That exception will occur when .NET 3 or higher is not installed, but it should be caught by the initialization routine. It will attempt to send you an email but should otherwise allow the gallery to function normally.

Check to see if you have GalleryServerPro.Business.Wpf.dll in your bin directory.

Well, after some more perusing of the database, I think I've found the problem but not sure exactly how to fix it. It seems that even though I changed the application name in the various providers of the web.config and GSP config file, GSP still created a new application entry in my aspnet_applications table, added my administrative user to the aspnet_Users table under the new application id and added the GSP system administrator role to the aspnet_Roles table under the new application id (also added a corresponding record in the aspnet_UsersInRoles table).

I'm working with pre-existing membership, role and profile providers (i.e. they existed in my app before adding Gallery Server Pro). Perhaps this has something to do with it so I'll add the configuration details that might be causing the problem.

Here's the data provider as specified in the gallery server pro config file

<dataProvider defaultProvider="SqlServerGalleryServerProProvider">
<providers>
<add applicationName="Satellite" connectionStringName="SystemFunctions"
name="SqlServerGalleryServerProProvider" type="GalleryServerPro.Data.SqlServer.SqlDataProvider" />
</providers>
</dataProvider>

SystemFunctions is a standard connection string for the local sqlserver

Next the membership provider...

<membership defaultProvider="SqlProvider" userIsOnlineTimeWindow="120">
<providers>
<clear />
<add connectionStringName="SystemFunctions" applicationName="Satellite"
enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true"
requiresUniqueEmail="true" passwordFormat="Hashed" minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="0" passwordStrengthRegularExpression="^\S{7,14}$"
name="SqlProvider" type="System.Web.Security.SqlMembershipProvider" />
</providers>
</membership>

Next the Role Provider...

<roleManager enabled="true" defaultProvider="myRoleProvider">
<providers>
<clear />
<add connectionStringName="SystemFunctions" applicationName="Satellite"
name="myRoleProvider" type="System.Web.Security.SqlRoleProvider" />
</providers>
</roleManager>

And finally the profile provider

<profile enabled="true" defaultProvider="myProfileProvider">
<providers>
<clear />
<add connectionStringName="SystemFunctions" applicationName="Satellite"
name="myProfileProvider" type="System.Web.Profile.SqlProfileProvider" />
</providers>
<properties>

...additional properties here...

<add name="ShowMediaObjectMetadata" defaultValue="false" type="String"
allowAnonymous="true" />
</properties>
</profile>

Hopefully, this will shed some light on the matter. Seems like it should work to me but then again, it's not so...

Thanks again. This looks like a great program and it feels like it's very close to working so I'm hopeful that the above will help find the problem.

p.s. I just realized that this posting is not in the correct forum for which I whole-heartedly apologize. Richard

Hi Roger,

I think this has something to do with the way the application set itself up in the database. As I stated in the previous post there are entries in the various membership tables (i.e. aspnet_applications, aspnet_users, etc.) that indicate two applications running instead of the one I would expect (i.e. my original application and the Gallery Server Pro application). GSP and my application should be running under the same application id (or at least that's how I envision it working). Seems like when the application got installed, it created a new application id and everything that goes along with it when what should have happened is that GSP should have used the existing application id. I'm going to run the debugging you suggested to see if it sheds further light but maybe the above will trigger an idea. Thanks. Richard

The error has nothing to do with the application name issue you refer to - at least I can't imagine how it could. In order to have the membership records you said you have in those tables, you must have run the GSP install wizard where one of the applicationName attributes was set to Gallery Server Pro. Since you changed the name, those records are no longer necessary and you may delete them.

That is helpful to report the line of code where the error is occurring, but it is baffling why it should fail. Here it is, along with the preceding line:



We can conclude GSP is finding the GalleryServerPro.Business.Wpf.dll but, because metadataExtractor is null, cannot find the WpfMetadataExtractor class inside it. Did you happen to change the namespace and/or class name in the WPF project? That is the only explanation that makes sense.

If that's not it, I don't know what else to suggest except to go back to the drawing board and put your testing cap on. Start with a standard GSP release and get it working. Then slowly modify it by editing web.config, etc, until you arrive at your current app setup.

Hi Roger,

Guess what? It's working! And I now know why it wasn't before. Seems this dummy sitting in my chair right now was using files from the source version that had not yet been compiled. I did compile the app to get the dll's but must have copied the other files before compiling. I replaced the files in the gs directory with the compiled versions and off it went. On a side note, I already had parts of the patterns and practices enterprise library installed in my app and had to update the object builder and common dlls with your versions to get things to work. Not sure why but then I'm not one to look a gift dll in the mouth. Sorry for the wild goose chase. Thanks for a great app. I'm looking forward to deploying it for our community users as soon as I've had a chance to get things configured correctly and tested. I'm thinking some kind of donation is in order as well. Thanks, Richard.

I have had this error on and off for a few days and never knew why and how. This thread lead me through the problem.

I am not sure if I did the right thing.

[Using the source version]
In the \Website\Properties\Post-build event command line, I copy all GSP dlls including \Website\bin\GalleryServerPro.Business.Wpf.dll to MyWebsite\bin

Problem:
1. The size of GSP Website\bin\GalleryServerPro.Business.Wpf.dll is 10752
2. The size of MyWebsite\bin\GalleryServerPro.Business.Wpf.dll is 4068

In the Project Build Order, TIS.GSP.Business.Wpf is the last one (after Website). and TIS.GSP.Business.Wpf.Resources is before Website. That's the reason! After Website is compiled, the post-build command copies GalleryServerPro.Business.Wpf.dll to MyWebsite\bin\. The size of this file is 4068. Then TIS.GSP.Business.Wpf compiles and generate a new GalleryServerPro.Business.Wpf.dll in GSP Website\bin\

Temp solution:
In Project Dependencies, set Website depends on TIS.GSP.Business.Wpf. It makes Website compiles after TIS.GSP.Business.Wpf is compiled; and I get a final version of GalleryServerPro.Business.Wpf.dll

Question in mind:
1. Why does TIS.GSP.Business.Wpf compiles after Website? There is no dependency relationship between them.
2. Why do TIS.GSP.Business.Wpf and TIS.GSP.Business.Wpf.Resources generate the same file name:
GalleryServerPro.Business.Wpf.dll ?

In the end, it was really difficult to come to the solution, after trying to debug the source code finding not much related to the cause. I have to say that I have very little experience dealing with so many related projects(including CommunityServer's) in a VS solution. The thing is getting more and more complicated, but more exciting though.

Out of curiosity, I reproduced the situation again.

1. Delete TIS.GSP.Business.Wpf.Resources\obj
2. Delete TIS.GSP.Business.Wpf\obj
3. Compile the solution

Found :
1. TIS.GSP.Business.Wpf.Resources\obj\Debug\GalleryServerPro.Business.Wpf.dll Size:4608
2. TIS.GSP.Business.Wpf\obj\Debug\GalleryServerPro.Business.Wpf.dll Size:10752
3. MyWebsite\bin\GalleryServerPro.Business.Wpf.dll Size:4608

Somehow, after \Website is compiled, (1) is copied to \Website\bin\ and my command copies \Website\bin\GalleryServerPro.Business.Wpf.dll to (3). Then, (2) is copied to Website\bin\

I can't tell how it happens. A few guesses:
1. In TIS.GSP.Business.Wpf.Resources Properties\Application\Assembly name = GalleryServerPro.Business.Wpf
2. The output path of TIS.GSP.Business.Wpf.Resources = ..\Website\bin\
3. In Project Dependencies, TIS.GSP.Business.Wpf depends on TIS.GSP.Business.Wpf.Resources

Still have no clue where this file was coming from:
TIS.GSP.Business.Wpf.Resources\obj\Debug\GalleryServerPro.Business.Wpf.dll Size:4608