Here are my experiences integrating my dottext 0.95 mods with the latest 0.96 codebase.

There were a number of hickups. Some were the kind of thing you expect from pre-release code (Grant Carpenter may need to checkin RichEditor.ascx.resx), but I also saw some development environment weirdness that made me wonder about how the threads used for search index generation interact with Visual Studio debugging?

I added the resx file to vaultpub if you want to see if that's your rebuild issue. I typically avoid including them unless I'm actually doing something with them; in this case, they're just there for the sake of VS.NET's convenience.

I had issues getting the referencing right in the Admin project between FTB 1.0 and 2.0. The current vaultpub source is using 2.0, so that might be in the compile issue mix.

There will be a couple additional hiccups with the development trunk as additional. There's a post from last week in which I laid out the current db schema modifications arising from the checked in membership changes.

I believe that there will be one and possibly two more schema changes as user profiles is finalized for 0.96 and ratings are added.

In other words, 0.96 is definitely pre-release code.

As far as the threading/devenv wierdness, I haven't really seen that personally, but I also haven't been working with search a lot to date.

I should add since you were discussing skins on your site, there will some changes to skins in 0.96, but they should be non-breaking changes. A pre-0.96 skin will just work, but it may be using supported yet obsolete controls/placeholders.

---

I'm Idaho!

Thanks for the quick reply Grant.
I added the resx file and the admin project rebuilds cleanly now.
I did try having VS auto generate a compatible resx file but failed. Perhaps there is some magic to avoid having to include resx files that don't contain any serious resources.

My skin already replaces some controls/placeholders from the standard ui/controls, adapting to a few more changes should be no big deal.

Part of the reason for doing the merge now was to minimize the amount of version skew. I had modified dozens of files along the way to getting a feel for the codebase which I've now reduced to just one (SimpleBlogService.asmx).

How could I go about getting write access to vaultpub and how is agreement reached among the developers on what features/changes to incorporate?

Tnx.

For commit access I think you have to talk to Scott. As far as agreement about features/changes, personally I've just asked for areas to work on in the past. As I have major changes/issues I go back and run through them with Scott.

So, in my experience, Scott is the center of the universe. All hail Scott. :)

---

I'm Idaho!