Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- From: "Earl" <brikshoe@xxxxxxxxxxxxxxxxx>
- Date: Thu, 22 Dec 2005 15:08:22 -0500
No betas installed. Not sure what happened, but the upgrade did not work.
The code came in but not the UI. Anyway, can you give me the best
recommendation for the signature capture, saving to a bitmap column in
SQLCE?
"Tim Wilson" <TIM(UNDERSCORE)WILSON(AT)ROGERS(PERIOD)COM> wrote in message
news:utGv4FyBGHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
> That's odd. I've upgraded projects and didn't have a problem. Maybe
> something went funky with the VS or SDK install. Did you have a VS 2005
> Beta
> installed before the RTM version? I know that people have seen issues due
> to
> the fact that the Beta was not completely removed... although I haven't
> heard anyone with your issue. In regards to the 3rd party stuff, with the
> design-time model change for Compact Framework controls/components, work
> needs to be done by the control authors to upgrade the controls to be VS
> 2005 compatible. I can say that this requires a fair amount of work to do
> as
> we're in the middle of porting the OpenNETCF controls and I believe this
> is
> primarily what's holding up the SDF 2.0 release.
>
> --
> Tim Wilson
> .NET Compact Framework MVP
>
> "Earl" <brikshoe@xxxxxxxxxxxxxxxxx> wrote in message
> news:OT7hqKwBGHA.3452@xxxxxxxxxxxxxxxxxxxxxxx
>> Ah, well, it's a commercial app that worked fine before Windows Mobile
>> 5.0
>> came out. Thus the upgrade.
>>
>> What got me into some hot water was jumping in to 2005 before I had the
> SDK
>> installed. Then apparently the skin was being applied to some but not all
>> forms -- that is now resolved. Unfortunately, that did not fix the need
>> to
>> do the UI redesign (almost done, 2 lost days), so I'm very leery of the
> idea
>> of a painless CF upgrade/import.
>>
>> At this point, all that's left is to investigate the suitability of
> Ginny's
>> recommended signature capture (was previously using the one by Rob
>> Tiffany
>> in VS2003), then test the data access, confirm that SQL Mobile plays nice
>> with SQL 2000 replication, and since the signature was going into the
> SQLCE
>> database, make that work again.
>>
>> On a related note, what I've also discovered in all of this is that none
> of
>> my 3rd party stuff is relevant to VS2005. Neither for the full framework
> nor
>> for the compact framework. This is going to be a strong disincentive for
>> folks to upgrade to 2005 -- buying tools again less than 2 years after
>> the
>> previous go-around. My approach for now will be to only upgrade the CF
> stuff
>> and leave the desktop alone (in particular, I'm not anxious to pay for
>> new
>> grids and reporting tools again this soon).
>>
>>
>> "Tim Wilson" <TIM(UNDERSCORE)WILSON(AT)ROGERS(PERIOD)COM> wrote in
>> message
>> news:%23aQdqQvBGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
>> > Can you zip up the solution and post it to the newsgroup or is this a
>> > project that others should not see? I'll open it at my end and see if I
>> > get
>> > the same behavior.
>> >
>> > --
>> > Tim Wilson
>> > .NET Compact Framework MVP
>> >
>> > "Earl" <brikshoe@xxxxxxxxxxxxxxxxx> wrote in message
>> > news:%23pZY8ktBGHA.3876@xxxxxxxxxxxxxxxxxxxxxxx
>> >> Seems unrelated Tim, but thanks for the insight.
>> >>
>> >> One oddity remains: my first designed form appears on the normal
>> >> design
>> >> surface, but all the forms I design after that have the emulator face
> as
>> > the
>> >> design surface. What is this all about?
>> >>
>> >>
>> >> "Tim Wilson" <TIM(UNDERSCORE)WILSON(AT)ROGERS(PERIOD)COM> wrote in
>> >> message
>> >> news:%23rRbYOlBGHA.532@xxxxxxxxxxxxxxxxxxxxxxx
>> >> > The reason I asked is because in VS 2005 there is a new design-time
>> > model
>> >> > that needs to be followed. If you have a control that is deemed
>> >> > "unsafe"
>> >> > to
>> >> > run on the desktop (due, primarily, to it's dependency on pinvokes),
>> > then
>> >> > you'll need to add a "design-time attributes" file to the project
>> >> > and
>> > mark
>> >> > the control class with the "DesktopCompatible" attribute.
>> >> >
>> >> > <DesktopCompatible>true</DesktopCompatible>
>> >> >
>> >> > Although this should not be the case with the built-in CF
>> >> > controls...
>> >> > these
>> >> > should be ready to go.
>> >> >
>> >> > --
>> >> > Tim Wilson
>> >> > .NET Compact Framework MVP
>> >> >
>> >> > "Earl" <brikshoe@xxxxxxxxxxxxxxxxx> wrote in message
>> >> > news:OfcoHSkBGHA.628@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> Some of the forms had custom controls on them, but not all. Yet all
> of
>> >> >> the
>> >> >> forms and all of the controls were rendered with the control name
>> >> >> only.
>> > I
>> >> >> ended up rebuilding the UI and pasting in the code-behind. It's
>> >> >> been
> a
>> >> > wacky
>> >> >> night with this VS2005 CF conversion! What does work has seemed
>> >> >> incredibly
>> >> >> sluggish. Seems like these tools are not quite
>> >> >> ready-for-prime-time.
>> >> >>
>> >> >> "Tim Wilson" <TIM(UNDERSCORE)WILSON(AT)ROGERS(PERIOD)COM> wrote in
>> >> >> message
>> >> >> news:O%23ZqqzjBGHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> > Are these custom controls that are rendering with the control
>> >> >> > name
>> > only
>> >> > on
>> >> >> > the design surface?
>> >> >> >
>> >> >> > --
>> >> >> > Tim Wilson
>> >> >> > .NET Compact Framework MVP
>> >> >> >
>> >> >> > "Earl" <brikshoe@xxxxxxxxxxxxxxxxx> wrote in message
>> >> >> > news:%23WO6t0gBGHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
>> >> >> >> Installed VS2005 the other day. No problem starting a new
> project,
>> >> >> > including
>> >> >> >> new device projects. However, when I go to import a CF project
> from
>> >> >> > VS2003,
>> >> >> >> the code-behind imports successfully, but for the components, I
> get
>> > a
>> >> >> >> flat
>> >> >> >> surface with simply the names of the controls in the Designer
> area.
>> >> > FWIW,
>> >> >> >> yes, the SDK is installed, altho I believe that is irrelevant to
>> >> >> >> the
>> >> >> > import
>> >> >> >> process.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>
.
- Follow-Ups:
- Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- From: Sergey Bogdanov
- Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- References:
- Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- From: Earl
- Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- From: Earl
- Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- From: Earl
- Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- From: Earl
- Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- Prev by Date: RE: Buttonbase and button event firing bugged
- Next by Date: Re: Buttonbase and button event firing bugged
- Previous by thread: Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- Next by thread: Re: Has anyone been able to successfully import a project from VS2003 CF to VS2005 CF?
- Index(es):
Relevant Pages
|
