When you remove a .NET assembly or type library from a Host Integration Server project, the file is not deleted and you receive a warning message in the Transaction Integrator (TI) Designer if you name a new .NET assembly or type library the same name
This article has been archived. It is offered "as is" and will no longer be updated.
The Microsoft Host Integration Server 2004 Transaction Integrator (TI) Designer still detects previously removed Microsoft .NET assemblies or type libraries (.tlb files) when a new .NET assembly or type library with the same name is created. When this behavior occurs, you receive a warning message that is similar to the following:
The file C:\Documents and Settings\Administrator\My Documents\Visual Studio Projects\TIProject1\TIProject1\Library1.dll already exists. Do you want to replace the existing file?
The same behavior occurs when you save the new .NET assembly or type library with a new name by using the Save As command. When a new Windows-initiated process (WIP) .NET Client Library is added, you receive an error message that is similar to the one in this section, even though the DLL was renamed previously.
The behavior occurs because when a object is removed from Solution Explorer, the file itself is not deleted.
This behavior is by design.
This is expected behavior. After an item is created, it is persisted within the project on the hard disk drive as a real file. When you save the file by using the Save As command, the original file is not deleted. Instead, the original file remains on the hard disk drive and another file with the new name is created.
The Transaction Integrator (TI) Designer error message is correct in prompting if you want to overwrite the real file that was previously created and put in the file system, even though the file does not show up in Solution Explorer.
Steps to reproduce the behavior
Start Microsoft Visual Studio .NET.
Create a new Host Integration Server project.
Add a WIP .NET Client Library. Use the default name "Library1", and then accept all subsequent default values when you complete the object. Library1.dll will now be listed under the project.
In Solution Explorer, remove Library1.dll from the project.
Add a WIP .NET Client Library that is named "Library1", and then accept all subsequent default values when you complete the object.
You receive the warning message that is described in the "Symptoms" section. The message indicates that Library1.dll already exists. However, this is incorrect because you removed Library1.dll in step 4 before you created the second DLL.