R
Rainer Queck
Hello Microsoft Support,
It looks like there is a bug inside the VS2008 Pro IDE.
I did quite a bit of debugging to narrow the problem down. Here is the
result of my efforts:
A VS2005 project compiles and runs fine, built in VS 2005 Pro.
This application displays a bunch of thumb jpg images using PictureBoxes on
its main Form. the PictureBoxes are created dynamically on startup.
After converting the project to VS2008 (german edition) with out doing any
changes on my side to the project, the PictureBoxes display the "red cross"
ErrorImages.
I found a workaround to this problem:
Loading my thumb jpgs not only to the PictureBox.Image but also to the
PictureBox.ErrorImage, the thumgs are displayed correct.
This alows the following conclutions:
- path to the thumb jpgs is correct
- size and format is correct
I have tried to build a demo project to reproduce this problem with out
succes.
The problem only occurs in my current Project.
I have minimized this project (now only 4MBb) and sent it to a german MVP.
He was able to reproduce the problem with it, but up to now also has no
solution to it.
What can I do get this issue solved?
Is it expedient to use up one of my "MSDN Support Incidents" for this?
Kind Regards
Rainer Queck
It looks like there is a bug inside the VS2008 Pro IDE.
I did quite a bit of debugging to narrow the problem down. Here is the
result of my efforts:
A VS2005 project compiles and runs fine, built in VS 2005 Pro.
This application displays a bunch of thumb jpg images using PictureBoxes on
its main Form. the PictureBoxes are created dynamically on startup.
After converting the project to VS2008 (german edition) with out doing any
changes on my side to the project, the PictureBoxes display the "red cross"
ErrorImages.
I found a workaround to this problem:
Loading my thumb jpgs not only to the PictureBox.Image but also to the
PictureBox.ErrorImage, the thumgs are displayed correct.
This alows the following conclutions:
- path to the thumb jpgs is correct
- size and format is correct
I have tried to build a demo project to reproduce this problem with out
succes.
The problem only occurs in my current Project.
I have minimized this project (now only 4MBb) and sent it to a german MVP.
He was able to reproduce the problem with it, but up to now also has no
solution to it.
What can I do get this issue solved?
Is it expedient to use up one of my "MSDN Support Incidents" for this?
Kind Regards
Rainer Queck