F
Fernando Chilvarguer
Hi all,
I just started using ASP.NET 2.0 Profile Providers and I have a question:
The scenario:
Without using the CreateUserWizard I:
1. Manually create a user
2. Manually create a profile for that user if the user is sucessfully
created.
3. Change some values of the profile.
4. Call myProfile.Save()
All works fine with the exception of fields that I do not specify a value.
Those fields are Null in the database, instead of the default value I gave
them on web.config.
If I manually set myProfile.PropertyValues["myField"].IsDirty = true then
the default value gets saved, but I wonder why I need to perform this step.
I have almost 50 fields like that, I'm trying to avoid having to do this to
every single one.
Any feedback is appreciated.
Thanks,
Fernando
I just started using ASP.NET 2.0 Profile Providers and I have a question:
The scenario:
Without using the CreateUserWizard I:
1. Manually create a user
2. Manually create a profile for that user if the user is sucessfully
created.
3. Change some values of the profile.
4. Call myProfile.Save()
All works fine with the exception of fields that I do not specify a value.
Those fields are Null in the database, instead of the default value I gave
them on web.config.
If I manually set myProfile.PropertyValues["myField"].IsDirty = true then
the default value gets saved, but I wonder why I need to perform this step.
I have almost 50 fields like that, I'm trying to avoid having to do this to
every single one.
Any feedback is appreciated.
Thanks,
Fernando