How can we help you today? How can we help you today?
richardjm
This a bug we've known about to do with the value having a false accuracy of say 1e-6 and another being 3e-6 but both being rounded to 0.0000 in the display. We simply ran out of time to look into it for this release. Well spotted though [image] / comments
This a bug we've known about to do with the value having a false accuracy of say 1e-6 and another being 3e-6 but both being rounded to 0.0000 in the display. We simply ran out of time to look into ...
0 votes
Bugmaster wrote: richardjm wrote: The add-in will always go via the wizard so that you can check the settings created automatically. I was with you until this last part... where are the settings created ? Is it an XML file somewhere ? The settings for the .NET Thing you're going to be evaluating are set automatically like the exe and the method filters. These you view in the wizard. Bugmaster wrote: If we supported one testing mechanism ( and we use nunit extensively within Red Gate) we'd clutter up the wizard even further and GBH would be committed upon me once more. No no, what I meant was, support it as dotTrace supports it. With dotTrace, when I'm looking at code in the VS IDE, I see little buttons on the left margin next to each method which has the [Test] attribute. The buttons, when clicked, show a popup menu: "Debug Test" and "Profile Test". When I click "Profile Test", dotTrace launches NUnit for me, and begins profiling the method, without going through wizards or configuration setups or anything like that. I do like this feature a lot. I don't imagine this happening for this version unless we get more people requesting it. It's easy enough to fire up Nunit using the VS Addin. It's most likely the startup project for the test cases anyway so doesn't involve any setting up. OK you do have to locate the test in your test cases and click play but it's hardly a hardship. We'll certainly look into it for future versions though as I can see that it would get a bit of a bind if you were doing it repetitively. Bugmaster wrote: Other than that I hope it's working well for you. We do after all allow line-level timings Is there a way to switch them into a percentage view ? As in, "your program spends 50% of its time in this line", vs., "Your program has spent this many milliseconds in this line". Simply - no, not at the moment, we're going to updating the facilities to visualise the problems soon though. / comments
Bugmaster wrote: richardjm wrote: The add-in will always go via the wizard so that you can check the settings created automatically. I was with you until this last part... where are the sett...
0 votes
You can turn off the wizard on startup by using the /nowizard command line argument. You can modify the shortcut to the program so that it will do this everytime you load. The add-in will always go via the wizard so that you can check the settings created automatically. I prefer the All methods tab with it's grouping, filtering and sorting abilities. There is also the hierarchy view where you can see calling functions and time spent and 'drill down' that way (ooooo marketing-speak). As I've commented elsewhere on the forum we're looking into doing a much more graphical ui for the next version so the tree view is certainly something we'll be looking at closely. I totally agree about the way it asked you to save two different things, I'm leaning towards a more solution based saving mechanism for the next version but it's still early days yet. It's an annoyance but at least you're reminded that you've got a project and results unsaved. Oleg commented elsewhere about a save button on the toolbar for the settings but it's a bit too cluttered as it is ( the UI designers and documenters would commit GBH if I added a button at this stage [image] ) Other people have commented on the popup menu getting auto-extended at the top. We're looking into fixes for this for the final release - that's what betas are for after all. NUnit - you're the first person to even mention it's support as far as i know. It's easy enough to run the nunit gui from ants - that's likely what the startup of an nunit dll is anyway to it would just work from the box via add-in. If we supported one testing mechanism ( and we use nunit extensively within Red Gate) we'd clutter up the wizard even further and GBH would be committed upon me once more. Other than that I hope it's working well for you. We do after all allow line-level timings [image] / comments
You can turn off the wizard on startup by using the /nowizard command line argument. You can modify the shortcut to the program so that it will do this everytime you load. The add-in will always go...
0 votes
I've been asked by David to respond as I'm the guy who's responsible for large parts of the engine of data compare... 1) Some scripts can be very large and take a long time to execute. If I did put in print statements say every 10 changes or say each table completed it could still add up quite quickly and there there would be as many people saying take out all those annoying print statments so it'd have to be an option. We can do it technically just finding a granularity that all can accept it the hard bit. 2) We treat the data transfer as an all or nothing, far better than having some tables migrated and others not. Say you have a reference to another table but no foreign key (it happens - a lot) we migrate the data table but fail to migrate the lookup table and the whole database starts to throw strange errors. Better to just fail and let the use figure out why the synchronization failed as they know their database far better than we could. Possibly better error checking could be integrated into the script but again this is a speed issue bear in mind some people are doing synchronizations that take several hours so adding anything would slow them down considerably. 3) If your target database has changed since you compared then you're using the wrong product. Much better to use the toolkit and have full control over when and how the scripts are generated. We're looking into another possible tool which may address this in the future. 4) I'll leave that for the UI guys. 5) We'll look at that where clause but it's a powerful feature that you can easily shoot yourself in the foot with [image] 6) Views are selected by default because in v4 and prior they were selected by default and we didn't want to change behaviour for v5. You can easily turn off indexed views in the options so they don't appear. Hope this helps. Richard (I feel like I've responded to six forum posts in one forum post [image] ) / comments
I've been asked by David to respond as I'm the guy who's responsible for large parts of the engine of data compare... 1) Some scripts can be very large and take a long time to execute. If I did put...
0 votes