Converting between compact and full framework projects (and vice versa)

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • bob

    #1

    Converting between compact and full framework projects (and vice versa)

    Hi

    Using 2003 - targeting the compact framework (c#), but would like to do most
    development using the full.net (manually leaving out stuff not in the
    compact framework).

    Q. Trying to find a way of converting a project to have builds for both
    compact and full. Project properties doesn't seem to help

    Thanks

    Bob


  • Tim Wilson

    #2
    Re: Converting between compact and full framework projects (and vice versa)

    You can build the project against the compact framework and the resulting
    assembly will run on the desktop. In other words, assemblies compiled
    against the compact framework are retargeted to the full framework when run
    on the desktop. So limiting yourself to types and members that exist in both
    frameworks and compiling against the compact framework is one way to go.
    Another way is to create one full framework project and one compact
    framework project and link to the same source files.

    --
    Tim Wilson
    ..NET Compact Framework MVP

    "bob" <bob@notthere.c om> wrote in message
    news:dq48h5$8dl $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...[color=blue]
    > Hi
    >
    > Using 2003 - targeting the compact framework (c#), but would like to do[/color]
    most[color=blue]
    > development using the full.net (manually leaving out stuff not in the
    > compact framework).
    >
    > Q. Trying to find a way of converting a project to have builds for both
    > compact and full. Project properties doesn't seem to help
    >
    > Thanks
    >
    > Bob
    >
    >[/color]


    Comment

    • bob

      #3
      Re: Converting between compact and full framework projects (and vice versa)

      Hi Tim

      Thanks for your quick response

      Your first suggestion is the one we are trying to do and does work.
      Unfortunately can't persuade the IDE to co-operate (!).
      Insists in trying to deploy to emulator or real portable device when
      debugging. Do you know if there is a way to add .net as a target, the
      Configuration manager seems not to offer any target option but the Pocket
      PC (and vice versa for a full .net project) - had a look at manually
      editing the project files - bit scary :)


      Bob


      "Tim Wilson" <TIM(UNDERSCORE )WILSON(AT)ROGE RS(PERIOD)COM> wrote in message
      news:%230NflNxF GHA.3624@TK2MSF TNGP09.phx.gbl. ..[color=blue]
      > You can build the project against the compact framework and the resulting
      > assembly will run on the desktop. In other words, assemblies compiled
      > against the compact framework are retargeted to the full framework when
      > run
      > on the desktop. So limiting yourself to types and members that exist in
      > both
      > frameworks and compiling against the compact framework is one way to go.
      > Another way is to create one full framework project and one compact
      > framework project and link to the same source files.
      >
      > --
      > Tim Wilson
      > .NET Compact Framework MVP
      >
      > "bob" <bob@notthere.c om> wrote in message
      > news:dq48h5$8dl $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...[color=green]
      >> Hi
      >>
      >> Using 2003 - targeting the compact framework (c#), but would like to do[/color]
      > most[color=green]
      >> development using the full.net (manually leaving out stuff not in the
      >> compact framework).
      >>
      >> Q. Trying to find a way of converting a project to have builds for both
      >> compact and full. Project properties doesn't seem to help
      >>
      >> Thanks
      >>
      >> Bob
      >>
      >>[/color]
      >
      >[/color]


      Comment

      • Tim Wilson

        #4
        Re: Converting between compact and full framework projects (and vice versa)

        AFAIK, you *can't* do this in VS .NET 2003. However, you can choose to
        simply build (not run or deploy) the solution and then go to the output
        directory and run the exe from there. You won't get the automatic debugging
        support that VS provides, although I'm sure that you could attach the
        debugger to the exe.

        A feature to allow this was actually explored in the earlier stages of VS
        2005. But it was cut.


        --
        Tim Wilson
        ..NET Compact Framework MVP

        "bob" <bob@notthere.c om> wrote in message
        news:dq4aqs$dun $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...[color=blue]
        > Hi Tim
        >
        > Thanks for your quick response
        >
        > Your first suggestion is the one we are trying to do and does work.
        > Unfortunately can't persuade the IDE to co-operate (!).
        > Insists in trying to deploy to emulator or real portable device when
        > debugging. Do you know if there is a way to add .net as a target, the
        > Configuration manager seems not to offer any target option but the Pocket
        > PC (and vice versa for a full .net project) - had a look at manually
        > editing the project files - bit scary :)
        >
        >
        > Bob
        >
        >
        > "Tim Wilson" <TIM(UNDERSCORE )WILSON(AT)ROGE RS(PERIOD)COM> wrote in message
        > news:%230NflNxF GHA.3624@TK2MSF TNGP09.phx.gbl. ..[color=green]
        > > You can build the project against the compact framework and the[/color][/color]
        resulting[color=blue][color=green]
        > > assembly will run on the desktop. In other words, assemblies compiled
        > > against the compact framework are retargeted to the full framework when
        > > run
        > > on the desktop. So limiting yourself to types and members that exist in
        > > both
        > > frameworks and compiling against the compact framework is one way to go.
        > > Another way is to create one full framework project and one compact
        > > framework project and link to the same source files.
        > >
        > > --
        > > Tim Wilson
        > > .NET Compact Framework MVP
        > >
        > > "bob" <bob@notthere.c om> wrote in message
        > > news:dq48h5$8dl $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...[color=darkred]
        > >> Hi
        > >>
        > >> Using 2003 - targeting the compact framework (c#), but would like to do[/color]
        > > most[color=darkred]
        > >> development using the full.net (manually leaving out stuff not in the
        > >> compact framework).
        > >>
        > >> Q. Trying to find a way of converting a project to have builds for[/color][/color][/color]
        both[color=blue][color=green][color=darkred]
        > >> compact and full. Project properties doesn't seem to help
        > >>
        > >> Thanks
        > >>
        > >> Bob
        > >>
        > >>[/color]
        > >
        > >[/color]
        >
        >[/color]


        Comment

        • bob

          #5
          Re: Converting between compact and full framework projects (and vice versa)

          Hi Tim

          Thanks for the info - saved a lot of hours trying to do the impossible!
          Pity it was dropped though, suspect it would have turned out to be one of
          the most important features for easy and quick development of compact
          framwork products.

          Cheers

          Bob



          "Tim Wilson" <TIM(UNDERSCORE )WILSON(AT)ROGE RS(PERIOD)COM> wrote in message
          news:%23IY1RMyF GHA.3728@tk2msf tngp13.phx.gbl. ..[color=blue]
          > AFAIK, you *can't* do this in VS .NET 2003. However, you can choose to
          > simply build (not run or deploy) the solution and then go to the output
          > directory and run the exe from there. You won't get the automatic
          > debugging
          > support that VS provides, although I'm sure that you could attach the
          > debugger to the exe.
          >
          > A feature to allow this was actually explored in the earlier stages of VS
          > 2005. But it was cut.
          > http://lab.msdn.microsoft.com/Produc...ckId=FDBK19279
          >
          > --
          > Tim Wilson
          > .NET Compact Framework MVP
          >
          > "bob" <bob@notthere.c om> wrote in message
          > news:dq4aqs$dun $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...[color=green]
          >> Hi Tim
          >>
          >> Thanks for your quick response
          >>
          >> Your first suggestion is the one we are trying to do and does work.
          >> Unfortunately can't persuade the IDE to co-operate (!).
          >> Insists in trying to deploy to emulator or real portable device when
          >> debugging. Do you know if there is a way to add .net as a target, the
          >> Configuration manager seems not to offer any target option but the
          >> Pocket
          >> PC (and vice versa for a full .net project) - had a look at manually
          >> editing the project files - bit scary :)
          >>
          >>
          >> Bob
          >>
          >>
          >> "Tim Wilson" <TIM(UNDERSCORE )WILSON(AT)ROGE RS(PERIOD)COM> wrote in
          >> message
          >> news:%230NflNxF GHA.3624@TK2MSF TNGP09.phx.gbl. ..[color=darkred]
          >> > You can build the project against the compact framework and the[/color][/color]
          > resulting[color=green][color=darkred]
          >> > assembly will run on the desktop. In other words, assemblies compiled
          >> > against the compact framework are retargeted to the full framework when
          >> > run
          >> > on the desktop. So limiting yourself to types and members that exist in
          >> > both
          >> > frameworks and compiling against the compact framework is one way to
          >> > go.
          >> > Another way is to create one full framework project and one compact
          >> > framework project and link to the same source files.
          >> >
          >> > --
          >> > Tim Wilson
          >> > .NET Compact Framework MVP
          >> >
          >> > "bob" <bob@notthere.c om> wrote in message
          >> > news:dq48h5$8dl $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...
          >> >> Hi
          >> >>
          >> >> Using 2003 - targeting the compact framework (c#), but would like to
          >> >> do
          >> > most
          >> >> development using the full.net (manually leaving out stuff not in the
          >> >> compact framework).
          >> >>
          >> >> Q. Trying to find a way of converting a project to have builds for[/color][/color]
          > both[color=green][color=darkred]
          >> >> compact and full. Project properties doesn't seem to help
          >> >>
          >> >> Thanks
          >> >>
          >> >> Bob
          >> >>
          >> >>
          >> >
          >> >[/color]
          >>
          >>[/color]
          >
          >[/color]


          Comment

          • Tim Wilson

            #6
            Re: Converting between compact and full framework projects (and vice versa)

            Yeah, it would have been a nice feature to have supported right out of the
            box.

            --
            Tim Wilson
            ..NET Compact Framework MVP

            "bob" <bob@notthere.c om> wrote in message
            news:dq58pq$177 $1@nwrdmz02.dmz .ncs.ea.ibs-infra.bt.com...[color=blue]
            > Hi Tim
            >
            > Thanks for the info - saved a lot of hours trying to do the impossible!
            > Pity it was dropped though, suspect it would have turned out to be one of
            > the most important features for easy and quick development of compact
            > framwork products.
            >
            > Cheers
            >
            > Bob
            >
            >
            >
            > "Tim Wilson" <TIM(UNDERSCORE )WILSON(AT)ROGE RS(PERIOD)COM> wrote in message
            > news:%23IY1RMyF GHA.3728@tk2msf tngp13.phx.gbl. ..[color=green]
            > > AFAIK, you *can't* do this in VS .NET 2003. However, you can choose to
            > > simply build (not run or deploy) the solution and then go to the output
            > > directory and run the exe from there. You won't get the automatic
            > > debugging
            > > support that VS provides, although I'm sure that you could attach the
            > > debugger to the exe.
            > >
            > > A feature to allow this was actually explored in the earlier stages of[/color][/color]
            VS[color=blue][color=green]
            > > 2005. But it was cut.
            > >[/color][/color]
            http://lab.msdn.microsoft.com/Produc...ckId=FDBK19279[color=blue][color=green]
            > >
            > > --
            > > Tim Wilson
            > > .NET Compact Framework MVP
            > >
            > > "bob" <bob@notthere.c om> wrote in message
            > > news:dq4aqs$dun $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...[color=darkred]
            > >> Hi Tim
            > >>
            > >> Thanks for your quick response
            > >>
            > >> Your first suggestion is the one we are trying to do and does work.
            > >> Unfortunately can't persuade the IDE to co-operate (!).
            > >> Insists in trying to deploy to emulator or real portable device when
            > >> debugging. Do you know if there is a way to add .net as a target, the
            > >> Configuration manager seems not to offer any target option but the
            > >> Pocket
            > >> PC (and vice versa for a full .net project) - had a look at manually
            > >> editing the project files - bit scary :)
            > >>
            > >>
            > >> Bob
            > >>
            > >>
            > >> "Tim Wilson" <TIM(UNDERSCORE )WILSON(AT)ROGE RS(PERIOD)COM> wrote in
            > >> message
            > >> news:%230NflNxF GHA.3624@TK2MSF TNGP09.phx.gbl. ..
            > >> > You can build the project against the compact framework and the[/color]
            > > resulting[color=darkred]
            > >> > assembly will run on the desktop. In other words, assemblies compiled
            > >> > against the compact framework are retargeted to the full framework[/color][/color][/color]
            when[color=blue][color=green][color=darkred]
            > >> > run
            > >> > on the desktop. So limiting yourself to types and members that exist[/color][/color][/color]
            in[color=blue][color=green][color=darkred]
            > >> > both
            > >> > frameworks and compiling against the compact framework is one way to
            > >> > go.
            > >> > Another way is to create one full framework project and one compact
            > >> > framework project and link to the same source files.
            > >> >
            > >> > --
            > >> > Tim Wilson
            > >> > .NET Compact Framework MVP
            > >> >
            > >> > "bob" <bob@notthere.c om> wrote in message
            > >> > news:dq48h5$8dl $1@nwrdmz03.dmz .ncs.ea.ibs-infra.bt.com...
            > >> >> Hi
            > >> >>
            > >> >> Using 2003 - targeting the compact framework (c#), but would like to
            > >> >> do
            > >> > most
            > >> >> development using the full.net (manually leaving out stuff not in[/color][/color][/color]
            the[color=blue][color=green][color=darkred]
            > >> >> compact framework).
            > >> >>
            > >> >> Q. Trying to find a way of converting a project to have builds for[/color]
            > > both[color=darkred]
            > >> >> compact and full. Project properties doesn't seem to help
            > >> >>
            > >> >> Thanks
            > >> >>
            > >> >> Bob
            > >> >>
            > >> >>
            > >> >
            > >> >
            > >>
            > >>[/color]
            > >
            > >[/color]
            >
            >[/color]


            Comment

            Working...