Comments
Sort by recent activity
Hi Chris
Thanks for your feedback.
We have already implemented this workaround. But it would be better to solve it with fixed components.
Thanks for your efforts.
Regards,
Demian / comments
Hi Chris
Thanks for your feedback.
We have already implemented this workaround. But it would be better to solve it with fixed components.
Thanks for your efforts.
Regards,
Demian
Hi Chris
It is fixed in this release:
Or the updated SDK with the new SQL Data compare engine here.
but not in the release here:
You can download the patch for SQL Data compare here.
Regards,
Demian / comments
Hi Chris
It is fixed in this release:
Or the updated SDK with the new SQL Data compare engine here.
but not in the release here:
You can download the patch for SQL Data compare here.
Regard...
Hi Chris
No, I don't mean the SQL Server script, I mean the .NET assemly thread culture 'Threading.Thread.CurrentThread.CurrentCulture'.
At the start of the program, the culture of 'Threading.Thread.CurrentThread.CurrentCulture' is set to 'de-CH', and when I pass the follow code block 01: Dim db1 As New Database
02: db1.RegisterForDataCompare(New ConnectionProperties(ssDBServerName, ssDBName, ssDBUsername, ssDBPassword), Options.Default)
03:
04: Dim db2 As New Database
05: db2.RegisterForDataCompare(New ConnectionProperties(sdDBServerName, sdDBName, sdDBUsername, sdDBPassword), Options.Default)
06:
07: Dim mappings As New SchemaMappings
08: mappings.CreateMappings(db1, db2)
09:
10: Dim session As New ComparisonSession()
11: session.CompareDatabases(db1, db2, mappings)
12:
13: Dim provider As New SqlProvider
14: Dim block As ExecutionBlock.ExecutionBlock = provider.GetMigrationSQL(session, True)
15:
16: Dim executor As ExecutionBlock.BlockExecutor = New ExecutionBlock.BlockExecutor
17: executor.ExecuteBlock(block, sdDBServerName, sdDBName, False, sdDBUsername, sdDBPassword)
then the culture of the assembly thread 'Threading.Thread.CurrentThread.CurrentCulture' has changed on execute 'CompareDatabases' in row '11: ...' to 'invariant culture'.
After that, the assemlby thread has an invalid culture to continue work, which will not set back by RedGate components.
Can you tell us why this appears?
Regards,
Demian
/ comments
Hi Chris
No, I don't mean the SQL Server script, I mean the .NET assemly thread culture 'Threading.Thread.CurrentThread.CurrentCulture'.
At the start of the program, the culture of 'Threading.Threa...