T
Tim Johnson
I want to continue building a CF v1.0 app under VS 2005. I've read a number
of the posts on how you can create an appname.config file to specify you
want to use CF v1.0 in the runtime environment (see
http://blogs.msdn.com/stevenpr/archive/2004/12/30/344540.aspx). But isn't
there also something you need to do in the IDE when compiling so it knows
which SDK assemblies to use? Otherwise what's to prevent me from
inadvertently using a CF v2.0-only feature, compling just fine, then failing
when running on a device with only CF v1.0 installed? The IDE lets me
specify debug vs. release, device vs. emulator, why not CF1 vs CF2?
Also it just seems strange I can build my CF1 app under VS2003 and deploy it
as just the exe, but do build the same app under VS2005 I have to also
deploy a config file even if the device doesn't contain CF2. What am I
missing?
--
Tim Johnson
High Point Software, Inc.
www.high-point.com
(503) 312-8625
of the posts on how you can create an appname.config file to specify you
want to use CF v1.0 in the runtime environment (see
http://blogs.msdn.com/stevenpr/archive/2004/12/30/344540.aspx). But isn't
there also something you need to do in the IDE when compiling so it knows
which SDK assemblies to use? Otherwise what's to prevent me from
inadvertently using a CF v2.0-only feature, compling just fine, then failing
when running on a device with only CF v1.0 installed? The IDE lets me
specify debug vs. release, device vs. emulator, why not CF1 vs CF2?
Also it just seems strange I can build my CF1 app under VS2003 and deploy it
as just the exe, but do build the same app under VS2005 I have to also
deploy a config file even if the device doesn't contain CF2. What am I
missing?
--
Tim Johnson
High Point Software, Inc.
www.high-point.com
(503) 312-8625