Bug report --- missing App.Config from controled project

rshillington · Post by **rshillington** » Thu Jun 14, 2007 11:33 am

The setup is VS 2005 SP1 and and Vault 2005 client, and Vault 4.0 server

With a Visual Bacic project already checked in, add an application setting from the Project / Properties -> Settings tab. This will create a new file called App.Config, which is not added to the change set. Check in the project and then App.Config file is left behind. I don't know for sure if it was like that on v3 but I think I would have noticed it it was.

Also as an aside if you watch the video you'll see that the project is not added to the repository tree in the place originally identified when the project was created.

I have a very short video (2 minutes) that illustrates the following problem (video is here)

Hopefully this is the best place to report this possible bug.

Regards,
Ralph Shillington
iFoundTime Inc. Ottawa, Canada.

lbauer · Post by **lbauer** » Thu Jun 14, 2007 1:52 pm

Look in the Vault Admin Client under Source Control Repositories-><Repository name> ->File Types. By default, .config is an excluded file. Excluded files are generally those not meant to be put under source control.

I'll have one of our developers take a look at the other issue of the location of the project in the tree.