VS2008

  • Thread starter Thread starter MDB
  • Start date Start date
M

MDB

Just wondering if anyone else out there is using VS2008 and if so, are you
experiencing it taking extremely long to build your mobile projects? It is
taking upwards to 5 minutes for mine to build.
 
I am upgrading from vs2003 so I figured why upgrade to vs2005 and cf 2.0
when 3.5 was released. I will try it in vs2005 and see how long it takes
using it.
 
How much memory do you have installed? Like Chris, I'm using VS 2008 and not
seeing any speed issues.
 
I am getting some conflicts when building and wonder if they have something
to do with it. Here is part of the build output, how do I "remap" the
assembly?





No way to resolve conflict between "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" and
"System, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089". Choosing "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes"
arbitrarily.


Consider app.config remapping of assembly "System.Xml, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "1.0.5000.0"
[C:\Windows\assembly\GAC\System.Xml\1.0.5000.0__b77a5c561934e089\System.Xml.dll]
to Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Windows.Forms,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Windows.Forms.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [] to Version
"2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Drawing, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "1.0.5000.0"
[] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Data, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0" []
to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Data.dll] to
solve conflict and get rid of warning.


Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.dll] to solve
conflict and get rid of warning.


C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning
MSB3247: Found conflicts between different versions of the same dependent
assembly.


C:\PMMobile 3.5\Controls\Disclaimers.cs(10,7): warning CS0105: The using
directive for 'System.ComponentModel' appeared previously in this namespace



C:\PMMobile 3.5\Classes\UserNotification.cs(296,75): warning CS0728:
Possibly incorrect assignment to local 'nt' which is the argument to a using
or lock statement. The Dispose call or unlocking will happen on the original
value of the local.



C:\PMMobile 3.5\OpenNetCF\MarshalEx.cs(33,3): warning CS3021:
'OpenNETCF.Runtime.InteropServices.MarshalEx' does not need a CLSCompliant
attribute because the assembly does not have a CLSCompliant attribute
 
Yes, that definitely has something to do with it. You have desktop
assemblies referenced and the compiler is not sure what to do about it.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com


MDB said:
I am getting some conflicts when building and wonder if they have something
to do with it. Here is part of the build output, how do I "remap" the
assembly?





No way to resolve conflict between "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" and
"System, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089". Choosing "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes"
arbitrarily.


Consider app.config remapping of assembly "System.Xml, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "1.0.5000.0"
[C:\Windows\assembly\GAC\System.Xml\1.0.5000.0__b77a5c561934e089\System.Xml.dll]
to Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Windows.Forms,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Windows.Forms.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [] to Version
"2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Drawing,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Data, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Data.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.dll] to
solve conflict and get rid of warning.


C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning
MSB3247: Found conflicts between different versions of the same dependent
assembly.


C:\PMMobile 3.5\Controls\Disclaimers.cs(10,7): warning CS0105: The using
directive for 'System.ComponentModel' appeared previously in this
namespace



C:\PMMobile 3.5\Classes\UserNotification.cs(296,75): warning CS0728:
Possibly incorrect assignment to local 'nt' which is the argument to a
using or lock statement. The Dispose call or unlocking will happen on the
original value of the local.



C:\PMMobile 3.5\OpenNetCF\MarshalEx.cs(33,3): warning CS3021:
'OpenNETCF.Runtime.InteropServices.MarshalEx' does not need a CLSCompliant
attribute because the assembly does not have a CLSCompliant attribute



I didn't see any major change from 03 to 05 either. There's got to be an
environment problem. I've not seen a 5 minute build for any managed
project.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



MDB said:
I am upgrading from vs2003 so I figured why upgrade to vs2005 and cf 2.0
when 3.5 was released. I will try it in vs2005 and see how long it takes
using it.


"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
Yes I'm using it. No builds take no longer than Studio 05.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



Just wondering if anyone else out there is using VS2008 and if so, are
you experiencing it taking extremely long to build your mobile
projects? It is taking upwards to 5 minutes for mine to build.
 
It must be one of the third party dlls then. I will have to check with
them. Thanks


Yes, that definitely has something to do with it. You have desktop
assemblies referenced and the compiler is not sure what to do about it.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com


MDB said:
I am getting some conflicts when building and wonder if they have
something to do with it. Here is part of the build output, how do I
"remap" the assembly?





No way to resolve conflict between "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" and
"System, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089". Choosing "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes"
arbitrarily.


Consider app.config remapping of assembly "System.Xml, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "1.0.5000.0"
[C:\Windows\assembly\GAC\System.Xml\1.0.5000.0__b77a5c561934e089\System.Xml.dll]
to Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Windows.Forms,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Windows.Forms.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [] to Version
"2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Drawing,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System.Data, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Data.dll]
to solve conflict and get rid of warning.


Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.dll] to
solve conflict and get rid of warning.


C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets :
warning MSB3247: Found conflicts between different versions of the same
dependent assembly.


C:\PMMobile 3.5\Controls\Disclaimers.cs(10,7): warning CS0105: The using
directive for 'System.ComponentModel' appeared previously in this
namespace



C:\PMMobile 3.5\Classes\UserNotification.cs(296,75): warning CS0728:
Possibly incorrect assignment to local 'nt' which is the argument to a
using or lock statement. The Dispose call or unlocking will happen on the
original value of the local.



C:\PMMobile 3.5\OpenNetCF\MarshalEx.cs(33,3): warning CS3021:
'OpenNETCF.Runtime.InteropServices.MarshalEx' does not need a
CLSCompliant attribute because the assembly does not have a CLSCompliant
attribute



I didn't see any major change from 03 to 05 either. There's got to be an
environment problem. I've not seen a 5 minute build for any managed
project.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



I am upgrading from vs2003 so I figured why upgrade to vs2005 and cf 2.0
when 3.5 was released. I will try it in vs2005 and see how long it
takes using it.


"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
Yes I'm using it. No builds take no longer than Studio 05.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



Just wondering if anyone else out there is using VS2008 and if so,
are you experiencing it taking extremely long to build your mobile
projects? It is taking upwards to 5 minutes for mine to build.
 
FYI: I posted a few months ago how moving from VS2003 to VS2005 made things
MUCH slower for me - I have 3GB and using just a fraction of that. Build
times are significantly longer, and the usability is way worse (IMHO). I
now do almost all my editting in VS2003 and occasionally compile with
VS2005. OK, don't flame me but, I can't help comparing the move from VS2003
to VS2005 to that of how people are describing the move from XP to Vista.

While I'm on a roll here, I'm amazed how simple things take so long; e.g.
Close all Windows can sometimes take quite a while. Why? Close Project (at
least in my case) should be almost instant; i.e. save one or two files,
write the new project file and be done. Yet it too takes a long time
(sometimes). Anyway, not bashing anyone here, but things sure are getting
more sluggish. Some I could swear there are lines like this:

// Intel paid us to do this
Thread.Sleep (500)

OK, just kidding...

I was working at a large company. The standard editor was emacs. I was
trying to convince the founders that we needed a real integrated IDE. I was
showing them an IDE an occasionally the IDE would do stuff for a second or
three (aka VS2005) and they started laughing: "Come on, we can't use that."

Hilton
 
Hilton,

Are you running Xp or Vista? I'm running Vista with 3GB and get good
performance with VS 2008. (It seems faster to me than 2005, but I can't be
sure since I rarely use 2005 any more.) I also have my disk set to defrag my
disk every night, which also made a huge difference in Xp on a previous
computer. If you aren't doing that regularly, it's worth a shot, especially
since saving stuff seems to take a long time on your machine.

No flames or bashing, but if anybody else has suggestions they're welcome.
Any by the way, it wasn't Intel but I'm pretty sure IBM did that at one
time. ;-) (Also kidding.)

--
Ginny Caughey
Device Application Development MVP


Hilton said:
FYI: I posted a few months ago how moving from VS2003 to VS2005 made
things MUCH slower for me - I have 3GB and using just a fraction of that.
Build times are significantly longer, and the usability is way worse
(IMHO). I now do almost all my editting in VS2003 and occasionally
compile with VS2005. OK, don't flame me but, I can't help comparing the
move from VS2003 to VS2005 to that of how people are describing the move
from XP to Vista.

While I'm on a roll here, I'm amazed how simple things take so long; e.g.
Close all Windows can sometimes take quite a while. Why? Close Project
(at least in my case) should be almost instant; i.e. save one or two
files, write the new project file and be done. Yet it too takes a long
time (sometimes). Anyway, not bashing anyone here, but things sure are
getting more sluggish. Some I could swear there are lines like this:

// Intel paid us to do this
Thread.Sleep (500)

OK, just kidding...

I was working at a large company. The standard editor was emacs. I was
trying to convince the founders that we needed a real integrated IDE. I
was showing them an IDE an occasionally the IDE would do stuff for a
second or three (aka VS2005) and they started laughing: "Come on, we can't
use that."

Hilton



Ginny Caughey said:
How much memory do you have installed? Like Chris, I'm using VS 2008 and
not seeing any speed issues.

--
Ginny Caughey
Device Application Development MVP


MDB said:
I am upgrading from vs2003 so I figured why upgrade to vs2005 and cf 2.0
when 3.5 was released. I will try it in vs2005 and see how long it takes
using it.


"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
Yes I'm using it. No builds take no longer than Studio 05.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



Just wondering if anyone else out there is using VS2008 and if so, are
you experiencing it taking extremely long to build your mobile
projects? It is taking upwards to 5 minutes for mine to build.
 
Ginny said:
Hilton,

Are you running Xp or Vista? I'm running Vista with 3GB and get good
performance with VS 2008. (It seems faster to me than 2005, but I can't be
sure since I rarely use 2005 any more.) I also have my disk set to defrag
my disk every night, which also made a huge difference in Xp on a previous
computer. If you aren't doing that regularly, it's worth a shot,
especially since saving stuff seems to take a long time on your machine.

My dev machine is XP. VS2003 compiles the project in 4 seconds, VS2005
takes 13 seconds. I compiled several times to make sure file system cache
misses weren't skewing the numbers. That's really significant - same
machine. An as I mentioned, 'real-time' editing is slower too.

Hilton



No flames or bashing, but if anybody else has suggestions they're welcome.
Any by the way, it wasn't Intel but I'm pretty sure IBM did that at one
time. ;-) (Also kidding.)

--
Ginny Caughey
Device Application Development MVP


Hilton said:
FYI: I posted a few months ago how moving from VS2003 to VS2005 made
things MUCH slower for me - I have 3GB and using just a fraction of that.
Build times are significantly longer, and the usability is way worse
(IMHO). I now do almost all my editting in VS2003 and occasionally
compile with VS2005. OK, don't flame me but, I can't help comparing the
move from VS2003 to VS2005 to that of how people are describing the move
from XP to Vista.

While I'm on a roll here, I'm amazed how simple things take so long; e.g.
Close all Windows can sometimes take quite a while. Why? Close Project
(at least in my case) should be almost instant; i.e. save one or two
files, write the new project file and be done. Yet it too takes a long
time (sometimes). Anyway, not bashing anyone here, but things sure are
getting more sluggish. Some I could swear there are lines like this:

// Intel paid us to do this
Thread.Sleep (500)

OK, just kidding...

I was working at a large company. The standard editor was emacs. I was
trying to convince the founders that we needed a real integrated IDE. I
was showing them an IDE an occasionally the IDE would do stuff for a
second or three (aka VS2005) and they started laughing: "Come on, we
can't use that."

Hilton



Ginny Caughey said:
How much memory do you have installed? Like Chris, I'm using VS 2008 and
not seeing any speed issues.

--
Ginny Caughey
Device Application Development MVP


I am upgrading from vs2003 so I figured why upgrade to vs2005 and cf 2.0
when 3.5 was released. I will try it in vs2005 and see how long it
takes using it.


"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
Yes I'm using it. No builds take no longer than Studio 05.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



Just wondering if anyone else out there is using VS2008 and if so,
are you experiencing it taking extremely long to build your mobile
projects? It is taking upwards to 5 minutes for mine to build.
 
Back
Top