We've been using uSiteBuilder for a couple of weeks now and it's great however i have a couple of questions about how others get around to following problems.
If a developer creates a new datatype that is not in my local DB it totally borks uSiteBuilder with an error. The datatype does not exist type error. At this point my idea is oh ok I'll create it but when i hit /Umbraco i get the same error so without removeing the dll and web.config tags i have no way of adding the Datatype. Is it possible to allow you to get to Umbraco without the error?
Is there going to be support for Creating datatypes at some point? This would be a great feature as it would fix the above problem.
uSiteBuilder seems to connect to the database before Umbraco does. This causes problem when you have an empty database and want to install. Again you have to remove the DLL and Web.config tags run the installer and then install it again. Is there anyway around this?
uSiteBuilder now finally allows you to not use a shared database :-) each dev can have their own.. it's that or commit often (in which case a VCS like Mercurial really shines)
They have said before there would be support coming, not sure what the status is.
Not sure how you'd "install" uSitebuilder before you set up a database? Yes, solution would be to temporarily remove those..
We are building option to disable uSiteBuilder synchronization using some web.config property. That might be the solution for your case. For now, when you get error like that, you can just remove dll that contains yoru document types, add data type, and put dll back. That's easier than removing uSiteBuilder dll and web.config change.
Aah, I misunderstood, you have this problem while not using a shared db. I didn't think of that, shame. I use Courier Express to update beta/live servers with new datatypes before copying over the uSitebuilder files, it could be an option for you to do that within your local network as well (but it's not very convenient either).
Following on from Vladan's comment, I find the simplest process is to comment out the offending doctype property, rebuild the site DLL and then add the custom datatype.
web.config flag will be really handy though, as on a big site the uSiteBuilder sync process can take a while, which is unecessary if you are just testing some page logic.
I'm working on some changes to uSiteBuilder that will create missing DataTypes. I have it working successfully locally but needs more testing and I will then submit a patch through CodePlex that would be good if they consider integrating back into the project.
The reason I was doing it to begin with was because the only show stopper I hit was the exception thrown on missing DataTypes so this kind of overcomes this problem however I have no clue yet how or if I can go about specifying settings for a datatype or even how it may behave if I add a thirdparty DataType e.g. from a package that is not yet installed. For now though it works fine with the OOTB datatypes.
No worries! :-) Interesting, interesting. I'm going to think about that, but just as a thought, aren't the settings saved in a single text field? In that case it'd be easy to provide them as a string. Not ideal, but it will allow you to more easily move datatypes between environments.
Yes I think they are saved as a single string however I need to be able to discover the settings for third party datatypes. I'm sure it is possible but will just take some time to investigate which I don't have at the moment bit hope to have a stab at it over xmas.
Multi Developer problem
Hi
We've been using uSiteBuilder for a couple of weeks now and it's great however i have a couple of questions about how others get around to following problems.
Again thanks for the package it's great
Jon
We are building option to disable uSiteBuilder synchronization using some web.config property. That might be the solution for your case. For now, when you get error like that, you can just remove dll that contains yoru document types, add data type, and put dll back. That's easier than removing uSiteBuilder dll and web.config change.
Thanks guys that web.config setting will come in very handy.
The DataType problems is a real killer when your using individual database and there does not seem to be a way around the issue.
Aah, I misunderstood, you have this problem while not using a shared db. I didn't think of that, shame. I use Courier Express to update beta/live servers with new datatypes before copying over the uSitebuilder files, it could be an option for you to do that within your local network as well (but it's not very convenient either).
Following on from Vladan's comment, I find the simplest process is to comment out the offending doctype property, rebuild the site DLL and then add the custom datatype.
web.config flag will be really handy though, as on a big site the uSiteBuilder sync process can take a while, which is unecessary if you are just testing some page logic.
I'm working on some changes to uSiteBuilder that will create missing DataTypes. I have it working successfully locally but needs more testing and I will then submit a patch through CodePlex that would be good if they consider integrating back into the project.
@Simon Something like this? http://our.umbraco.org/projects/developer-tools/usitebuilder-import
Not really, takes more of a code-first approach like building new sites with uSiteBuilder so you can do something like this:
/// /// Defines the Standard Content Editor Datatype /// [DataType( UniqueId = "{8AB81EFB-35F5-4EF0-9300-04A3AC8A2D21}", Name = "Standard Content Editor", DatabaseDataType = DBTypes.Ntext, RenderControlGuid = "5e9b75ae-face-41c8-b47e-5f4b0fd82f83")] public class StandardContentEditor : DataTypeBase { }Aah, well you set DocTypes, not DataTypes, that looks AWESOME!
It looks like it's going to be difficult though, especially to support the settings of the datatypes as well.
Ooops! I've updated the post now - sorry.
The reason I was doing it to begin with was because the only show stopper I hit was the exception thrown on missing DataTypes so this kind of overcomes this problem however I have no clue yet how or if I can go about specifying settings for a datatype or even how it may behave if I add a thirdparty DataType e.g. from a package that is not yet installed. For now though it works fine with the OOTB datatypes.
No worries! :-) Interesting, interesting. I'm going to think about that, but just as a thought, aren't the settings saved in a single text field? In that case it'd be easy to provide them as a string. Not ideal, but it will allow you to more easily move datatypes between environments.
Yes I think they are saved as a single string however I need to be able to discover the settings for third party datatypes. I'm sure it is possible but will just take some time to investigate which I don't have at the moment bit hope to have a stab at it over xmas.
Cheers, Si
Yeah, no worries, it'll probably end up being a sort-of export anyway, as the values are stored in a wide variety of ways.. :)
is working on a reply...