'ProfileCommon is ambiguous

[whatsthehampton]

Hi all,

I have enabled Profiles in the web.config as so;

<profile enabled="true" defaultProvider="JBSqlProfileProvider">
<providers>
<remove name="AspNetSqlProvider"/>
<add name="JBSqlProfileProvider" connectionStringName="jbData" applicationName="/jbxel_iskool" type="System.Web.Profile.SqlProfileProvider, System.Web, Version=2.0.3600.0, &#xA;Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</providers>
<properties>
<add name="FirstName" type="string"/>
<add name="FamilyName" type="string"/>
</properties>
</profile>

The project builds without errors and everything works as it should locally - even with the live site connection string. However, on the live server I get 'ProfileCommon' is ambiguous.
Both sites are identical.

Is there a way to flush out the temporary asp.net files on the live server? Maybe that would help??

Many thanks,

j

http://www.bst.ac.jp

 

[jshurst]

Not sure, but have you tried restarting IIS?

From a command prompt:

iisreset

I've had problem's when copying the precompiled folder to my server. I now delete the old files from the server (making a backup first, of course ;-) ) first then copy the new ones over (don't know why, but I haven't had any problems now that I'm doing it this way).

 

[whatsthehampton]

Thank you jshurst,

I wish I could try resetting iss but its a shared host.

I have narrowed it down to...

Either set <profile enabled="false">

or,

<properties>
'remove all property names from here
</properties>

Both allow the site to run but of course I can't use profiles then.

Any other ideas I could try please?

Cheers,
j

http://www.bst.ac.jp

 

[whatsthehampton]

Cracked it!

Here's my answer that will hopefully help the next victim.

I am using the Web Deployment Project to build my sites.
You need to deploy your PrecompiledApp.config as well othewise the profile provider will be built twice.

Doh!

j

http://www.bst.ac.jp