DO 4.3 RC4. 1. Open VS 2. Create new project (and new solution) from DO Model template (goes with Person class sample) 3. Add new standard console application project to the solution 4. Add model project (2) reference to console application (3) 5. Add "new Person();" line into Main() of console project 6. Build. Observation (or may be bug?): VS complains for type Person. We must be missing the reference. VS didn't copy model project output assembly to console project bin.
Bug (!?): VS still complains for the Person. Manual says "upgrade project" can do whatever is needed to make it working. Does it? If we created console project from DO template it would reference model projects with ease. Updated at 04.07.2010 11:51:11I've found the cause of problem. It's because VS2010 creates console projects with client profile. I guess your udater should warn user that project cannot be instrumented because it uses client profile. This thread was imported from our support forum. The original discussion may contain more detailed answer. Original topic by marmon. |
Ups, yes. Actually, this will be fixed soon: currently Xtensive.Storage references System.Web (because of Xtensive.Storage.Web.SessionManager), which isn't a part of .NET 4 Client Profile. But quite soon it will be moved to optional Xtensive.Practices.Web. We just should finish up with the current release (4.3). |
Can you publish its .csproj file here? I'll say what's wrong.
Most likely, DataObjects.Net assemblies + its .targets file aren't referenced. If there is a result of bug in upgrade tool, we'll fix this.