ssmorgan

I get this error any time I check a file into TFS.

Visual Studio has service pack 1 installed

Team Server has service pack 1 installed.

What have I done wrong and how do I make this error go away.

Files do get checked in ok.




Re: Team Foundation Server - Version Control Object reference not set to an instance of an object

Ben Ryan - MSFT

Are you performing the checkin using the right-click context menu in Source Control Explorer

If so, does performing the checkin from the Pending Changes toolwindow complete without showing this error

If the answer to both of these is "yes", then you most likely are encountering an issue that is fixed in the upcoming release of VS. The error is relatively harmless since the checkin does complete prior to throwing this error.

If you did not answer "yes" to the questions above, then it would be helpful to know:

1) Does the error occur on checkin from Source Control Explorer

2) Does the error occur on checkin from Solution Explorer

3) Does the error occur on checkin from Pending Changes toolwindow

4) Does the error occur only when a solution is loaded or regardless of there being a solution open

Thanks,
Ben Ryan






Re: Team Foundation Server - Version Control Object reference not set to an instance of an object

ssmorgan

Ben,

Yes, the check-in is using the right-click context menu in Source Control Explorer.

There is only one dialog box that appears after the right-click context menu selection of "check-in pending changes".

It is titled "Check In - Source Files - Workspace: myworkstationName"

with the Source Files, Work Items, Check-in Notes, Policy Warnings tabs on the left.

It is this dialog box that I select "check-in" and afterwards that the pop error occurs.

If you have a beta of the upcomming release, I could test to see if this bug is fixed or not.

The projects have solutions and are generally open with VS 6.0, but the projects seem only partially mapped in 6.0 (The workspace is connected, but not all the project files) Not quite sure how to fix the source control mapping in the 6.0 .dsp and .dsw files. I was reluctant to do "add to source control" since the projects already exist in TFS, andI don't want to end up with 2 copies of the project in TFS.

While I concluded that the error was relatively harmless, since the check-in does work, But I would like it to go away.






Re: Team Foundation Server - Version Control Object reference not set to an instance of an object

Michal Malecki - MSFT

Hello,

to download beta1, please look at Brian's blog:

http://blogs.msdn.com/bharry/archive/2007/05/03/all-orcas-beta-1-downloads-are-now-available.aspx

It was released some time ago so you may want to read more about it before installing it.

Could you elaborate about problem you have with working in VS 6.0 (VC 6.0 ) Do you use TFS Msscci provider If the project exists already on the server you may try doing "Open from Source Control" (make backup of the project first) - I think the dsp and dsw files should be fixed than. In VS 2003 it is possible do bind existing project to the server location, but I'm afraid there is no similar option in VS 6.0






Re: Team Foundation Server - Version Control Object reference not set to an instance of an object

ssmorgan

Yes I am using the TFS MSSCCI provider with 6.0

So I tried "Open from Source Control" on a 6.0 project that I didn't have changes in progress on.

However, I had to open it twice "Open from Source Control" before the source control binding got repaired.

This changed the .dsw file, even though it MSCCI didn't check it out first.

However, even after the binding was correct (in vs 6.0 and with the project still open).

I then check-out and checked in the .dsw file from VS2005 and still get the same dialog popup

"Object not set to an instance of an object" error.






Re: Team Foundation Server - Version Control Object reference not set to an instance of an object

ssmorgan

So Orcas is going to be VS2007 or VS2008

looks like the cutoff for feedback from Beta 1 was end of May, and more than I have time for right now.

I was hoping for more like a VS 2005 service pack 2 beta.






Re: Team Foundation Server - Version Control Object reference not set to an instance of an object

Michal Malecki - MSFT

Afaik:

I have not heard about VS 2005 SP2

The official name for Orcas is VS2008 but it doesn't mean that we will wait for the next year to release it