How can we help you today? How can we help you today?
dwainew
OUCH, saved a draft a few days ago, and now it's gone.... ugh. The page you've called out helps me understand why the app is working the way it does, but not how to use it in the wild. The real question is how to get the truth into TFS. What's the workflow? I'm used to being able to tell source control what the truth is based on my knowledge of the state of the project, not having the tooling dictate which direction information can flow. This is probably me not having that ah-ha moment of understanding, so please, set me strait! Using the page you've referenced as an example, I'd like to call out the moment I start to stumble... If we compare Amanda's database and the scripts folder in source control, we can see a table in Amanda's database that isn't in source control. We don't have any information about where the difference came from, so we can't tell whether we should commit that table to source control or drop it from Amanda's database. Shouldn't it be up to AMANDA what to do with the table? She's the dev and knows what her intent is. The table should show on both the commit tab as an add (to push the table to SCS) AND the get latest tab as a drop from the database. my situation is this.... Amanda commits the table from her local db to TFS and labels this as v1. Amanda is informed by the master of her universe that v2 now lives on server xyz. (v2 is actually an empty db, so the table isn't there) Amanda opens SSMS and links xyz.db to the same TFS node with the intent of checking in v2. To her surprise, SSC shows (by way of the icon in object explorer) that there are no differences! The commit tab shows nothing. Are v1 and v2 identical? Out of curiosity, Amanda views the Get latest tab and sees that there IS A DIFFERENCE between the DB and TFS that was otherwise unknown to her and SSC is offering to add the table to the v2 db. What should Amanda do? She knows the new db is the truth, but can't check it in because SSC is only offering to go from TFS to DB. / comments
OUCH, saved a draft a few days ago, and now it's gone.... ugh. The page you've called out helps me understand why the app is working the way it does, but not how to use it in the wild. The real q...
0 votes
Originally I was comparing the DB to a previously cloned version. However, even comparing the DB to itself gives the error. / comments
Originally I was comparing the DB to a previously cloned version. However, even comparing the DB to itself gives the error.
0 votes
Dan, Of course you need a time limit, but setting it the same as that of a full release version is pretty restrictive, especially when it expires even before the release date! This is the first instance I've ever seen that situation. Your first Beta had no time limit, right? At least I didn't notice, because I ran it, liked the concept, spent a few days playing and commenting on the forum, and then got board and forgot about it till Beta 2. If you're concerned about the Beta 2 harming sales, make it a time limit that extends beyond the projected release date by 30 or 45 days... It's not going to kill your sales, as those that are using it often are GOING TO BUY THE REALEASE!! Those that don't weren't going to buy it anyway so an extra month of use is irrelevant to red-gate. But then again, why would someone bother beta testing a product they have no interest in using? And, why would you ever want to treat beta testers just like some user trying a demo? They are spending their time HELPING you with a product that, by definition, isn't ready for prime time. If you think you can release a working product that fully solves the majority of users' needs and has no bugs, based solely on developers' opinions, I've got some land to sell you in Florida! Has red-gate learned nothing from MS's new approach using CTPs and "interactive" product development? / comments
Dan, Of course you need a time limit, but setting it the same as that of a full release version is pretty restrictive, especially when it expires even before the release date! This is the first in...
0 votes
I had just changed the Application Options to use a different SQL editor. I used double quotes for the path, since it was in progra~1... removing the dbl quotes prevents the exception. / comments
I had just changed the Application Options to use a different SQL editor. I used double quotes for the path, since it was in progra~1... removing the dbl quotes prevents the exception.
0 votes