Article ID: 885002 - View products that this article applies to.
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 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 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 behavior occurs because when a object is removed from Solution Explorer, the file itself is not deleted.
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