Vista - Feb CTP can't generate an application definition

The FEB CTP can't compile the MyApp.xaml file. It insists of doing the
following

namespace ApplicationX {
using ...


instead of puttin the using statement outside of the namespace like it
does for a page or a windows, i.e.

using ....
namespace Application X{


I'm reverting back to the January CTP. Hopefully, the next CTP works a
bit better...

Phil

Philippe-
Sorry to hear of the problem.

When I look at MyApp.g.cs in obj\debug under my project and compare that to
Page1.g.cs, they both have
namespace ApplicationX {
using ...

So I am not sure what you mean that Page an ApplicationDefinition work
differently.

You were talking about the code generated during build in .g.cs files,
right?

Can you give us a small project that shows the problems you are having? Or
describe them in more detail.
What compile or runtime errors are you getting?

Thanks,
Rob Relyea
WPF, PM
http://longhornblogs.com/rrelyea


"Philippe Lavoie" <philippe.lavoie@cactus.ca> wrote in message
news:%23jaKnmrRGHA.4384@tk2msftngp13.phx.gbl...
> The FEB CTP can't compile the MyApp.xaml file. It insists of doing the
> following
>
> namespace ApplicationX {
> using ...
>
>
> instead of puttin the using statement outside of the namespace like it
> does for a page or a windows, i.e.
>
> using ....
> namespace Application X{
>
>
> I'm reverting back to the January CTP. Hopefully, the next CTP works a bit
> better...
>
> Phil

I checked with the Jan CTP and the behavior is indeed to have the using
inside the namespace.

The errors I had were related to the fact that if I'm mapping to a local
data structure. If I would set the clr-namespace to

xmlns:src="clr-namespace:ApplicationX.Data"

then it would complain that it couldn't find the namespace
ApplicationX.ApplicationX.Data

the same would happen for the code behind Class

x:Class="ApplicationX.Page1"

would give me, can't find ApplicationX.ApplicationX.Page1

and x:Class="Page1" would give me an error with the generated code
which would state that it was missing a parameterless constructor.

I hope this helps. I'm typing this from memory because I removed the Feb
CTP. I need to produce a demo soon and not being able to generate the
application file kind of prevented that

Phil



Rob Relyea [MSFT] wrote:
> Philippe-
> Sorry to hear of the problem.
>
> When I look at MyApp.g.cs in obj\debug under my project and compare that to
> Page1.g.cs, they both have
> namespace ApplicationX {
> using ...
>
> So I am not sure what you mean that Page an ApplicationDefinition work
> differently.
>
> You were talking about the code generated during build in .g.cs files,
> right?
>
> Can you give us a small project that shows the problems you are having? Or
> describe them in more detail.
> What compile or runtime errors are you getting?
>
> Thanks,
> Rob Relyea
> WPF, PM
> http://longhornblogs.com/rrelyea
>
>
> "Philippe Lavoie" <philippe.lavoie@cactus.ca> wrote in message
> news:%23jaKnmrRGHA.4384@tk2msftngp13.phx.gbl...
>
>>The FEB CTP can't compile the MyApp.xaml file. It insists of doing the
>>following
>>
>>namespace ApplicationX {
>> using ...
>>
>>
>>instead of puttin the using statement outside of the namespace like it
>>does for a page or a windows, i.e.
>>
>>using ....
>>namespace Application X{
>>
>>
>>I'm reverting back to the January CTP. Hopefully, the next CTP works a bit
>>better...
>>
>>Phil
>
>
>

That using-inside-the-namespace thing is a standard that I saw mentioned in
one of Brad Abrams (he worked on API standards for a while) as the preferred
way of doing things. ASP.Net user controls automatically get generated that
way, but other classes do not; I emailed him for an explanation as to the
rule, since I haven't found anything saying what the effect even is, but
never got a response. I really dislike rules/standards that are proposed
without an kind of explanation, but if the compiler is now trying to enforce
that, it's even more frustrating.