Comments
Sort by recent activity
necessary to dropping assemblies consecutively - according to dependencies between them.
in compare5.2 assemblies dropping without regard dependencies between them.
necessary (step-by-step):
1. drop all functions and procedures, founded on assembly
2. drop all assemblies with provision for dependencies
3. create all assemblies with provision for dependencies
4. create all functions, which are founded on assembly / comments
necessary to dropping assemblies consecutively - according to dependencies between them.
in compare5.2 assemblies dropping without regard dependencies between them.
necessary (step-by-step):
1. dro...
"So does AtWDModel & AtWinManufact have a .NET reference to Atechnology.winDraw.Model?"
YES! / comments
"So does AtWDModel & AtWinManufact have a .NET reference to Atechnology.winDraw.Model?"
YES!
assembly Atechnology.winDraw.Model must dropped on last step! / comments
assembly Atechnology.winDraw.Model must dropped on last step!
at 83 line in script:
PRINT N'Dropping CLR assemblies'
GO
DROP ASSEMBLY [Atechnology.winDraw.Model]
GO
DROP ASSEMBLY [AtWinManufact]
GO
DROP ASSEMBLY [AtWDmodel]
GO
go to Management Studio->database->... and see to dependencies
of AtWinManufact or AtWDmodel.
they have a dependency from Atechnology.winDraw.Model / comments
at 83 line in script:
PRINT N'Dropping CLR assemblies'
GO
DROP ASSEMBLY [Atechnology.winDraw.Model]
GO
DROP ASSEMBLY [AtWinManufact]
GO
DROP ASSEMBLY [AtWDmodel]
GO
go to Management Studio->databas...
Project configuration->
Options->
More Options...->
Behavior->
Do not use transactions in sync... - YES
Do not use ALTER ASSEBLY to change CLR types - YES / comments
Project configuration->
Options->
More Options...->
Behavior->
Do not use transactions in sync... - YES
Do not use ALTER ASSEBLY to change CLR types - YES
do once again comparison of these bases,
with that OPTIONS of the comparison, about which I wrote.
call attention - in violin invalid sequence removing of the assemblies! / comments
do once again comparison of these bases,
with that OPTIONS of the comparison, about which I wrote.
call attention - in violin invalid sequence removing of the assemblies!
recreate assemblies with provision for dependencies... / comments
recreate assemblies with provision for dependencies...
:-)
problem1 - dependencies between all assembly of the base!
After compare going to the script: -> line numbers 85-89
dropping assemblies without dependencies!
correct sequence:
DROP ASSEMBLY [AtWinManufact]
GO
DROP ASSEMBLY [AtWDmodel]
GO
DROP ASSEMBLY [Atechnology.winDraw.Model]
GO / comments
:-)
problem1 - dependencies between all assembly of the base!
After compare going to the script: -> line numbers 85-89
dropping assemblies without dependencies!
correct sequence:
DROP ASSEMBLY [AtW...
I consider that me necessary to send you two my databases.
data in base not will - an archive will be small.
where and to whom send?
this will vastly accelerate searching for of the mistake. / comments
I consider that me necessary to send you two my databases.
data in base not will - an archive will be small.
where and to whom send?
this will vastly accelerate searching for of the mistake.
thank, david!
the problem with names function is locked.
but that with relationship between assembly? / comments
thank, david!
the problem with names function is locked.
but that with relationship between assembly?