P
Paul [Paradise Solutions]
Hey all
To mention but four, over the last 3 weeks I've have the following
problems that I cannot seem to be able to solve.
1) Events. I had a set of custom events working in a project (6 in
total). After a compile one day I noticed that they had stopped firing.
Taken out of the project and into another (in an attempt to reproduce
for this forum) they work fine (exact copy/paste). Are there
'invisible' things that are legal to code but have an impact on event
functionality?
2) Corruption of Solution files. As mentioned earlier by myself, all my
references from the main project to other projects in the solution 'blew
up' with "Unknown Error"s listed in the task list (all of which were
working last week) and all function/method/object names in the drop down
lists were replaced by 2 entries of "Empty" across the entire solution.
I was unable to solve the problem working with the existing solution
file, so I deleted it and reconstructed (~seems~ to be working now).
3) MSCordll / Referencing compiled custom CF DLLs. Created a new smart
device project of class library type and created a couple of classes for
generic use. Compiled the project. Created second smartdevice
application to consume DLL. On creating the reference VS informed me
that the DLL I was referencing may not be compatible with the platform I
wanted to run on, but allows it none the less. After accepting that, a
tasklist error pops up stating that there is a conflict with MSCordll.
Now, I have noticed that there aer many posts about this, but most are
where the MSCoredll version numbers are different. As my custom DLL and
Application were ~both~ created with the CF, the error stated MSCoredll
was in essence conflicting with itself (I do not have references to
MScoredll in either of the projects). Some people say not to reference
the DLL directly (why?), but instead, bring the project into your
solution and reference that. Fine, appart from then you are prone to "I
can't compile because something somewhere has a lock on the file... I
think" errors, which would imply timing issues inside VS.
And finally...
4) Window focus/activation. Various threads have been / are in
existance regarding form focus relyability, such as being able to switch
between modal forms of the same app (all be it with the first one
locked, but still cycled by the OS when selecting the same task more
than one in the task list (or your PDAs equivilent), and anther
apparently random issue that I have right now - fire up my code (no
errors) and the application starts fine... apart from the form not being
visible to the user as the application has decided to load 'underneath'
the Today page (with the exception of the inputbar, which brings itself
to the front). There is no code on the form that adjusts window focus
or visibility, apart from that which I have put in, in an attempt to
make the form visible (none of which have any effect) which include
BringToFront() and Visible=True .
I'm sure I'm not the only one who has notice and/or experienced the
above. Was wondering if anyone is able to shed light on them, or if
there are any proposed bug fixes for VS2003 (or is the bug fix called
VS2004?).
For reference, I program agains a Compaq iPaq3700 series PPC2002 running
CF sp1 and a DEll Axim X5 PPC2003 CFsp1, language used is VB.net
Many thanks for reading this (if you made it this far) - I hope I can
one day be as much help to you as people have been to me.
Paul
To mention but four, over the last 3 weeks I've have the following
problems that I cannot seem to be able to solve.
1) Events. I had a set of custom events working in a project (6 in
total). After a compile one day I noticed that they had stopped firing.
Taken out of the project and into another (in an attempt to reproduce
for this forum) they work fine (exact copy/paste). Are there
'invisible' things that are legal to code but have an impact on event
functionality?
2) Corruption of Solution files. As mentioned earlier by myself, all my
references from the main project to other projects in the solution 'blew
up' with "Unknown Error"s listed in the task list (all of which were
working last week) and all function/method/object names in the drop down
lists were replaced by 2 entries of "Empty" across the entire solution.
I was unable to solve the problem working with the existing solution
file, so I deleted it and reconstructed (~seems~ to be working now).
3) MSCordll / Referencing compiled custom CF DLLs. Created a new smart
device project of class library type and created a couple of classes for
generic use. Compiled the project. Created second smartdevice
application to consume DLL. On creating the reference VS informed me
that the DLL I was referencing may not be compatible with the platform I
wanted to run on, but allows it none the less. After accepting that, a
tasklist error pops up stating that there is a conflict with MSCordll.
Now, I have noticed that there aer many posts about this, but most are
where the MSCoredll version numbers are different. As my custom DLL and
Application were ~both~ created with the CF, the error stated MSCoredll
was in essence conflicting with itself (I do not have references to
MScoredll in either of the projects). Some people say not to reference
the DLL directly (why?), but instead, bring the project into your
solution and reference that. Fine, appart from then you are prone to "I
can't compile because something somewhere has a lock on the file... I
think" errors, which would imply timing issues inside VS.
And finally...
4) Window focus/activation. Various threads have been / are in
existance regarding form focus relyability, such as being able to switch
between modal forms of the same app (all be it with the first one
locked, but still cycled by the OS when selecting the same task more
than one in the task list (or your PDAs equivilent), and anther
apparently random issue that I have right now - fire up my code (no
errors) and the application starts fine... apart from the form not being
visible to the user as the application has decided to load 'underneath'
the Today page (with the exception of the inputbar, which brings itself
to the front). There is no code on the form that adjusts window focus
or visibility, apart from that which I have put in, in an attempt to
make the form visible (none of which have any effect) which include
BringToFront() and Visible=True .
I'm sure I'm not the only one who has notice and/or experienced the
above. Was wondering if anyone is able to shed light on them, or if
there are any proposed bug fixes for VS2003 (or is the bug fix called
VS2004?).
For reference, I program agains a Compaq iPaq3700 series PPC2002 running
CF sp1 and a DEll Axim X5 PPC2003 CFsp1, language used is VB.net
Many thanks for reading this (if you made it this far) - I hope I can
one day be as much help to you as people have been to me.
Paul