References in Smart Device projects do not work in team development. 'If a reference is embedded in a project, and the project is checked into the source control, and then another user enlists in the project, the reference is broken when the other user opens the project. Because the reference is broken, the dynamic link library is not found, and the user receives the following error message:
The .NET assembly '<class library>' could not be found.
This behavior occurs because the Reference Path
setting is not set in the project file when a new enlistment occurs.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET 2003 Service Pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
25-Sep-2003 20:32 7.10.3268.0 1,490,944 Msevbprj.dll
25-Sep-2003 20:32 7.10.3268.0 999,424 Esproj.dll
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.