views:

223

answers:

2

Hi

I'm using asp.net profile functionality. I need to use some profile property names like "test/appname".

When I try to star the web application I get an error about invalid property name. I think the problem is the autogenerated profilecommon class.

I'm accesing profile properties with getters and setters so I don't need the profilecommon class

How can I avoid this class creation?

A: 

Is this a Website project or a Web Application project?

EDIT

http://stackoverflow.com/questions/426609/asp-net-membership-how-to-assign-profile-values

Check the part about having to implement profiles yourself for the Web Project - also MVC AFAIK: http://www.codersbarn.com/post/2008/07/10/ASPNET-PayPal-Subscriptions-IPN.aspx

IrishChieftain
It's a web application project, I'm using ASP.net MVC
I don't speak english. I think I make the wrong question.I need to avoid the creation of profilecommon.In my test project I'm using profile properties like: appname1/title1 or appname2/title2I need the "/" in the name of the property (is a requiremente), and I'm accesing the profile with the profilebase. In the test all work ok, but when I try to use this functionallity in asp.net, I have an error about propery name invalid in the web.config. I think the problem is the dynamic creation of the profilecommon with name properties using "/"
Can you give a code sample and indicate what type of ASP.NET project this is?
IrishChieftain
Here is a code sample, it's a 2.83k rar compressed filehttp://www.mediafire.com/?kjmm4mzuvmmIt's only an empty website with the profile section, net 3.5, created with VS2008. You dont need the database to run the website.If you don't comment the properties with slashes, the website doesn't work
I cannot open this. Why would you need a slash in a property name?
IrishChieftain
Customer requirement ...
Can you not simply use "appname" and resolve any path issue in your code and/or DB?
IrishChieftain
A: 

Hi,

I think that Rodrigo wants to -prevent- the ProfileCommon class automatic generation because he needs to use property names which include slashes and other invalid member names characters (which work fine for property names).

Is that possible? Can I prevent (avoid) the ProfileCommon class generation (provided I need to define the properties inside the profile seccion in Web.config).

Thanks

Carlos Peix
Yes Carlos, this is what I need, thanks for the clarification ;)