Comments
Sort by recent activity
- Have you checked that the resource is in the assembly
- Are you in your trial period for the SDK. (Do you get nag dialogs appearing when running the application locally)
- What is the error which is thrown on failure / comments
- Have you checked that the resource is in the assembly
- Are you in your trial period for the SDK. (Do you get nag dialogs appearing when running the application locally)
- What is the error which...
Is the licenses.licx file set with Build Action "Embedded Resource" and included in the root directory of your project(s)?
From the knowledge base article I linked above
"Don't copy the licenses.licx file from another folder manually, for instance using a command prompt or Windows Explorer. It should be added as a new item at the Visual Studio project level with a build action of "Embedded Resource"
In order to check that the licx file is correctly included you can use reflector
"If a licence file produced as the result of a successful activation is present on the build computer, the build will silently succeed. To double-check that your assembly has been licensed successfully,
you may use a tool such as .NET Reflector (http://reflector.red-gate.com/download.aspx), open your assembly, expand 'resources', locate a resource called <YourAssemblyFileName>.licenses, view the resource, and make sure that the resource contains 'RedGate.SQLCompare.Engine.Database' and also 'RedGate.SQLDataCompare.Engine.ComparisonSession' if you had also referenced the Data Compare Engine in your project." / comments
Is the licenses.licx file set with Build Action "Embedded Resource" and included in the root directory of your project(s)?
From the knowledge base article I linked above
"Don't copy the licenses.li...
If you compile an application against the Comparison SDK with a licenses.licx file (as per the samples http://www.red-gate.com/sqltoolkit/latestsamples/sql_data_compare_API ) the application should be able to run on any machine without requiring a license.
If you have problems this article ( http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Comparison%20SDK&c=knowledgebase%5cSQL_Comparison_SDK%5cKB200710000160.htm ) has more information.[/url] / comments
If you compile an application against the Comparison SDK with a licenses.licx file (as per the samples http://www.red-gate.com/sqltoolkit/latestsamples/sql_data_compare_API ) the application should...
Try
- Make sure both tables are unmapped (select them in the top pane and click unmap)
- Select WidgetPrices on the left of the bottom pane
- Select WidgetPricesNew on the right of the bottom pane
- Click map.
Hope that helps. / comments
Try
- Make sure both tables are unmapped (select them in the top pane and click unmap)
- Select WidgetPrices on the left of the bottom pane
- Select WidgetPricesNew on the right of the bottom pane
...
Have you seen this help topic? http://www.red-gate.com/supportcenter/C ... c43727.htm
You can get there by pressing F1 on the mapping tab. / comments
Have you seen this help topic?http://www.red-gate.com/supportcenter/C ... c43727.htm
You can get there by pressing F1 on the mapping tab.
This is due to a limitation in the CHM viewer. The pages are included in the .chm file, but cannot be viewed if it is on a network drive, or via a UNC path. http://support.microsoft.com/kb/896358
There is a workaround here http://www.technipages.com/unable-to-open-chm-files-on-a-network-drive.html which should fix the problem. / comments
This is due to a limitation in the CHM viewer. The pages are included in the .chm file, but cannot be viewed if it is on a network drive, or via a UNC path.http://support.microsoft.com/kb/896358
T...
Bill, It may be worth noting that SQL Prompt will allow you to recover those scripts. In version 4 you can hover over the object name and click the yellow tooltip. The script pane will come up with the complete script.
If you are using the SQL Prompt 5 EAP you can right click on the object name and "Script object as alter", which avoids hitting this (and several other) bugs in SSMS's script object as alter. / comments
Bill, It may be worth noting that SQL Prompt will allow you to recover those scripts. In version 4 you can hover over the object name and click the yellow tooltip. The script pane will come up w...
Another option is to attach the Visual Studio debugger and put exception catch on only for InvalidOperationException.
[Ctrl + Alt E] / comments
Another option is to attach the Visual Studio debugger and put exception catch on only for InvalidOperationException.
[Ctrl + Alt E]
Assembly.CodeBase is still set.
string codeBase = assembly.CodeBase;
string localPath = new Uri(codeBase).LocalPath;//NOTE: assembly.Location will often be "" because of {SA}
I'm not sure if this behaviour is guaranteed in {SA} / comments
Assembly.CodeBase is still set.
string codeBase = assembly.CodeBase;
string localPath = new Uri(codeBase).LocalPath;//NOTE: assembly.Location will often be "" because of {SA}
I'm not sure if this b...
Hey peter. Sorry again about the problem, we're working on fixing it, but I for now I'm just going to flesh out the work around. Once you've committed the assembly to source control we are unable to show the tab, but if it never goes into source control (or we cunningly delete it) then the tab will still work. That means that you can carry on trying out the product by never committing the assembly.
In order to delete the assembly you can
- Delete the assemblies sql file using your normal source control client and commit
- You then need to go and update your WorkingBase folder manually using your source control client. If you look in C:\Users\<whoever>\AppData\Local\Red Gate\SQL Source Control 1\WorkingBases for the file you just deleted in source control, and then update the Assemblies directory containing it the file should disappear
- If you then restart SSMS the tab should now load without error, showing the Assembly as an Add on the commit tab. / comments
Hey peter. Sorry again about the problem, we're working on fixing it, but I for now I'm just going to flesh out the work around. Once you've committed the assembly to source control we are unabl...