Vista - "Assembly attribute" errors after moving to Jan CTP

I was working fairly happily with Nov CTP. Then I moved PC's and took the
opportunity to move to Jan CTP.
Now every XAML file with a mapping flags an Assembly atribute error that I
can't seem to get round, and no references in XAML to my own classes seem to
be acceptable. I'm suddenly looking at 186 errors I can't seem to fix
(though in successive compiles with no code change that number fluctuates -
I've seen it as low as 45)

I've found just enough about this issue on the web to know I'm not alone but
still don't know how to move forward. Is this a cider issue ? Can I turn it
off ?

Thanks in advance.

--
Griff
(trying to make an industrial UI with XAML/WPF/c#)

Since posting this I have chased this problem round and round in circles.

I have started seeing weirder and weirder results and am slowly losing my
grip.
For example:
- error messages relating (by line and column number) to code that is
clearly located inside comments in XAML
- error messages such as:
The type '(one of my classes)' already contains a definition for
'_contentLoaded' C:\Documents and Settings\(blah)me\My Documents\Visual
Studio 2005\Projects\(blah)\obj\Debug\(classname).g.cs

That is to say, an error whose location is only specified in terms of the
..g.cs file the compiler creates, but which seems to have no direct cause
inthe actual source file (which, incidentally, was fine 3 days ago before
whatever went wrong went wrong).

I guess it is something to do with my installation because a copy from
sourcesafe from last time this project successfully compiled acts just as
weird.

But this is pretty much a vanilla install of XP/VS2005 and the Jan CTP on a
clean XP PC on Monday.

Anyone got any ideas which bits of VS can get this messed up ?






--
Griff
(trying to make an industrial UI with XAML/WPF/c#)


"Griff" wrote:

> I was working fairly happily with Nov CTP. Then I moved PC's and took the
> opportunity to move to Jan CTP.
> Now every XAML file with a mapping flags an Assembly atribute error that I
> can't seem to get round, and no references in XAML to my own classes seem to
> be acceptable. I'm suddenly looking at 186 errors I can't seem to fix
> (though in successive compiles with no code change that number fluctuates -
> I've seen it as low as 45)
>
> I've found just enough about this issue on the web to know I'm not alone but
> still don't know how to move forward. Is this a cider issue ? Can I turn it
> off ?
>
> Thanks in advance.
>
> --
> Griff
> (trying to make an industrial UI with XAML/WPF/c#)

Is it likely that you still have the older version of the SDK (or at least
WPF libraries that the SDK installed) on your machine?

--
Ashish Shetty [MSFT]
Program Manager, Windows Presentation Foundation (Avalon)
Blog: http://nerddawg.blogspot.com
---
This posting is provided "AS IS" with no warranties, and confers no rights.


"Griff" <Griff@discussions.microsoft.com> wrote in message
news:602C7E69-E00B-45F5-88C0-FA89C102D099@microsoft.com...
> Since posting this I have chased this problem round and round in circles.
>
> I have started seeing weirder and weirder results and am slowly losing my
> grip.
> For example:
> - error messages relating (by line and column number) to code that is
> clearly located inside comments in XAML
> - error messages such as:
> The type '(one of my classes)' already contains a definition for
> '_contentLoaded' C:\Documents and Settings\(blah)me\My Documents\Visual
> Studio 2005\Projects\(blah)\obj\Debug\(classname).g.cs
>
> That is to say, an error whose location is only specified in terms of the
> .g.cs file the compiler creates, but which seems to have no direct cause
> inthe actual source file (which, incidentally, was fine 3 days ago before
> whatever went wrong went wrong).
>
> I guess it is something to do with my installation because a copy from
> sourcesafe from last time this project successfully compiled acts just as
> weird.
>
> But this is pretty much a vanilla install of XP/VS2005 and the Jan CTP on
> a
> clean XP PC on Monday.
>
> Anyone got any ideas which bits of VS can get this messed up ?
>
>
>
>
>
>
> --
> Griff
> (trying to make an industrial UI with XAML/WPF/c#)
>
>
> "Griff" wrote:
>
>> I was working fairly happily with Nov CTP. Then I moved PC's and took
>> the
>> opportunity to move to Jan CTP.
>> Now every XAML file with a mapping flags an Assembly atribute error that
>> I
>> can't seem to get round, and no references in XAML to my own classes seem
>> to
>> be acceptable. I'm suddenly looking at 186 errors I can't seem to fix
>> (though in successive compiles with no code change that number
>> fluctuates -
>> I've seen it as low as 45)
>>
>> I've found just enough about this issue on the web to know I'm not alone
>> but
>> still don't know how to move forward. Is this a cider issue ? Can I
>> turn it
>> off ?
>>
>> Thanks in advance.
>>
>> --
>> Griff
>> (trying to make an industrial UI with XAML/WPF/c#)