How to disable creating vc80.idb file by VS2005 ?


R

Rud0x1

VS2005 writes and reads this file during building a project. So, ClearCase
think that it is one of sources file.
 
Ad

Advertisements

M

Mitesh Bulsara

I guess you are using module attribute in your project.

This attribute creates those files which define the starting points of your application.

You may do away with module attribute by creating main functions and giving your own definitions to DllGetClassObject, DllRegisterServer, etc. funtions.

I hope this helps.

Cheers
Mitesh



Rud0x wrote:

How to disable creating vc80.idb file by VS2005 ?
02-Mar-09

VS2005 writes and reads this file during building a project. So, ClearCase
think that it is one of sources file.

Previous Posts In This Thread:

How to disable creating vc80.idb file by VS2005 ?
VS2005 writes and reads this file during building a project. So, ClearCase
think that it is one of sources file.


Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF GridView Sample To Insert, Update, and Delete Records
http://www.eggheadcafe.com/tutorials/aspnet/fc9a5bf6-f5bb-4443-a92a-c9a46fd3aeb2/wpf-gridview-sample-to-in.aspx
 
Ad

Advertisements

M

Mitesh Bulsara

I guess you are using module attribute in your project.

This attribute creates those files which define the starting points of your application.

You may do away with module attribute by creating main functions and giving your own definitions to DllGetClassObject, DllRegisterServer, etc. funtions.

I hope this helps.

Cheers
Mitesh



Rud0x wrote:

How to disable creating vc80.idb file by VS2005 ?
02-Mar-09

VS2005 writes and reads this file during building a project. So, ClearCas
think that it is one of sources file.

Previous Posts In This Thread:

How to disable creating vc80.idb file by VS2005 ?
VS2005 writes and reads this file during building a project. So, ClearCas
think that it is one of sources file.

Replace module attribute
I guess you are using module attribute in your project.

This attribute creates those files which define the starting points of your application.

You may do away with module attribute by creating main functions and giving your own definitions to DllGetClassObject, DllRegisterServer, etc. funtions.

I hope this helps.

Cheers
Mitesh


Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Binding Beyond the Limitation of Name Scopes
http://www.eggheadcafe.com/tutorials/aspnet/ef583104-e507-491d-b05f-49faac8854c8/wpf-binding-beyond-the-li.aspx
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top