jwcolby
jwcolby at colbyconsulting.com
Thu Feb 9 06:51:25 CST 2012
>You would need a setup with a SQL Server replication master having the different SQLEXPRESS instances as replication slaves. Or? Wait for it to grow up a little? John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 2/9/2012 7:31 AM, Gustav Brock wrote: > Hi Shamil > > No, I haven't tried that. Thanks for the warning. > > Now, this is nothing compared to the troubles with LightSwitch. This _insists_ on a local SQLEXPRESS instance. So what to do if you switch workstation (home and work for example)? You would need a setup with a SQL Server replication master having the different SQLEXPRESS instances as replication slaves. Or? > > /gustav > > >>>> Salakhetdinov Shamil<mcp2004 at mail.ru> 09-02-2012 12:57>>> > Hi Gustav -- > > I mainly meant project files (.csproj for C#) > > Try to add/delete/rename project items for the same project on two different PCs. > Then try to merge changed projects into common source code repository... > > Thank you. > > -- Shamil > > 09 февраля 2012, 14:54 от "Gustav Brock"<Gustav at cactus.dk>: >> Hi Shamil >> >> As I recall it, the SVN worked fine except for the database connection string in the config file. So either you have to edit that string after each check-in, or you had to exclude the config file from the versioning system. >> >> And isn't it so that you can exclude the sln file in any case. Isn't it mostly for your local setup and won't change much as long as its collection of projects is not changed? I haven't looked into this - normally it "just works". >> >> /gustav >> >>>>> Salakhetdinov Shamil<mcp2004 at mail.ru> 05-02-2012 20:21>>> >> <snip> >> To minimize the level of "heroism" there should be first of all one technical task solved, namely: >> >> - Visual Studio solution files (.sln) and project files (.csproj (C#)) aren't possible(?) to check-out from a source control system (SVN, or HG, or ...) by several developers in parallel and then check-in back without laborious manual work on resolving collisions, and so within the above mentioned project the decision was to not let VS solution and project files to check-out/check-in at all - and that decision imposed quite some additional work on coordinators... >> >> If anybody knows effective resolution of this check-in/check-out of edited/changed VS solution and project files issue then coordination work would become a matter of magnitude less "heroic", still there should be two or more coordinators who commit to actively participate in a project under development and three to ten developers who commit but aren't sure will they have time or not to do the work they commit for - then there are good chances a project will be completed in planned time with low level of "heroism"... >> </snip> > > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com >