It does not seem possible to build Umbraco 4.0.2.1 for anything other than ASPNET 3.5 (this is based on downloading the source code and trying to rebuild the system within VS 2008). Is that correct? Targeting ASPNET 2 causes a problem because System.Web.Extensions.Design can't be referenced.
The reason this may be important is that I am currently running into oddball problems getting my umbraco site, which runs fine on a development server using ASPNET 3.5, to run properly on a hosted site. Yet if I do a clean install onto the hosted site Umbraco runs fine there, too. I think the "incompatibilities" between ASPNET 2 and ASPNET 3.5 are causing me problems when I upload DLLs compiled for the newer target onto the hosting company's server.
As to why I'm rebuilding Umbraco: there's a bug in how 4.0.2.1 handles password recovery using the UmbracoMembershipProvider. Basically, password recovery doesn't work in the distributed code, because the encrypted password is not decrypted before being returned by the recovery method. I've submitted the bug on codeplex, but it hasn't been addressed yet :).
Put another way, can someone explain to me how to rebuild Umbraco targeting ASPNET 2? I might be able to rebuild the binaries for the older target, upload them to the hosting company, and fix my problem.
No, according to the hosting company they include the extensions when you select "ASPNET 2". In fact, they say that selecting ASPNET 2 actually gets you ASPNET 3.5.
Building Umbraco 4.0.2.1
It does not seem possible to build Umbraco 4.0.2.1 for anything other than ASPNET 3.5 (this is based on downloading the source code and trying to rebuild the system within VS 2008). Is that correct? Targeting ASPNET 2 causes a problem because System.Web.Extensions.Design can't be referenced.
The reason this may be important is that I am currently running into oddball problems getting my umbraco site, which runs fine on a development server using ASPNET 3.5, to run properly on a hosted site. Yet if I do a clean install onto the hosted site Umbraco runs fine there, too. I think the "incompatibilities" between ASPNET 2 and ASPNET 3.5 are causing me problems when I upload DLLs compiled for the newer target onto the hosting company's server.
As to why I'm rebuilding Umbraco: there's a bug in how 4.0.2.1 handles password recovery using the UmbracoMembershipProvider. Basically, password recovery doesn't work in the distributed code, because the encrypted password is not decrypted before being returned by the recovery method. I've submitted the bug on codeplex, but it hasn't been addressed yet :).
Put another way, can someone explain to me how to rebuild Umbraco targeting ASPNET 2? I might be able to rebuild the binaries for the older target, upload them to the hosting company, and fix my problem.
- Mark
Do you need to install the ASP.NET extensions on your development machine?
No, according to the hosting company they include the extensions when you select "ASPNET 2". In fact, they say that selecting ASPNET 2 actually gets you ASPNET 3.5.
- Mark
I meant on your local machine... when you're trying to rebuild Umbraco... do you have the extensions installed?
Yes, I do.
- Mark
I have problem answer directly, look at http://our.umbraco.org/forum/ourumb-dev-forum/bugs/5041-Posting-reply-problem
v4.0.2.1 was compiled against the ASP.NET AJAX v1 extensions. You need to make sure that those are installed before it'll compile.
.NET 3.5 brought in updated assemblies which are the same name, as they were included into the .NET framework rather than as a separate install.
is working on a reply...