Hi, I've been asked to create an Umbraco site but use a load of functionality from an existing webforms asp.net VB site. I have a few concerns:
The existing site uses it's own membership system which has thousands of members each with lots of data. Much of what the new site will show will depend on the role of the member. So, can Umbraco be set to use the members table in the existing database sensibly in this regard?
I intend to use Umbraco MVC and C# for the new site. Can I mix VB webforms code (as macros) and C# MVC views (partial views) as I don't want to have to re-write all the existing VB code.
Am I being too "bleeding edge" here for a what's supposed to be a low(ish) budget prototype site?
You can certainly implement a custom membership provider in Umbraco, so I don't think 1) should be a problem. For 2) the main issue you'll have here is if you use any code-behind events or anything that relies on view state. Not tried it, but I believe it'll work otherwise but that may not be very useful if you lose that functionality... hence you'd either need to use Web Forms rather than MVC or rewrite your user controls using surface controllers and partial views.
I think their budget won't stretch to the effort required for a full code re-write just now, which would be the best way to do this going forward. So I've reluctantly advised the client not to use Umbraco at this stage. Simply(!) clone their existing site and repurpose it for now. Should the new business take off then the preferred option would be Umbraco for the future. Their current site is a 10 year old, twice re-written site with an absolute ton of wierd, out of the blue, odd, business rules. To get the best out of Umbraco, it all needs a good re-architecting. Not something to be done at short notice, like this is.
Strategic integration advice
Hi, I've been asked to create an Umbraco site but use a load of functionality from an existing webforms asp.net VB site. I have a few concerns:
Hi Craig
You can certainly implement a custom membership provider in Umbraco, so I don't think 1) should be a problem. For 2) the main issue you'll have here is if you use any code-behind events or anything that relies on view state. Not tried it, but I believe it'll work otherwise but that may not be very useful if you lose that functionality... hence you'd either need to use Web Forms rather than MVC or rewrite your user controls using surface controllers and partial views.
Hope that helps.
Andy
Thanks Andy,
I think their budget won't stretch to the effort required for a full code re-write just now, which would be the best way to do this going forward. So I've reluctantly advised the client not to use Umbraco at this stage. Simply(!) clone their existing site and repurpose it for now. Should the new business take off then the preferred option would be Umbraco for the future. Their current site is a 10 year old, twice re-written site with an absolute ton of wierd, out of the blue, odd, business rules. To get the best out of Umbraco, it all needs a good re-architecting. Not something to be done at short notice, like this is.
Cheers,
Craig
is working on a reply...