active reports files broken

[zumafan]

When we loaded our new source controlled visual studio 2003 solutions to each developer's machine, it looks like the links between the Active Reports.NET *.rpx and *.vb files was broken, which causes problems for the active reports report editor.

I'm not sure if this a Visual Studio problem or a sourcegear problem, but does anyone have any insight into how to fix this?

[dan]

Can you explain this a little more? Do you mean that when you check one file out it doesn't automatically check out the other file too?

[Zumafan]

Yes, exactly. Up until we converted to using sourcecontrol, all of the .vb files were nested below their respective .rpx files (the same way a .aspx.vb file is nested). Once we converted, this nesting was lost.

The good news is that we copied all of the rpx/vb files out of the working folder, deleted them from the project file, re-added them, and they appeared with the proper nesting. Problem solved.

Again I'm not sure if this is a VS thing, but you may want to look into it because, like I said, it happened when we moved to a sourcegear setup.


Thanks for the quick response!

[dan]

VS is very picky about where files need to be in order to be under source control. In some instances it copies files where it needs them to be, which can be really confusing.

However, the only way to really know whether it is VS or Vault is to try the same operation with SourceSafe as the SCC provider and see if you get the same behavior. Since that will probably be troublesome for you, and it is working now, I'd suggest enjoying the holiday instead