NicoVB Posted June 25, 2002 Posted June 25, 2002 I've added an image to the project and set it to 'Embedded Resource'. But how do I call this resource in code?? Greetz Quote Visit http://www.nico.gotdns.com Now ONLINE!
*Gurus* Thinker Posted June 26, 2002 *Gurus* Posted June 26, 2002 I would look into the ResourceManager class. Looks like images are a bit of a pain. You might also need to look into the resxgen and resgen tools. Quote Posting Guidelines
*Gurus* divil Posted June 26, 2002 *Gurus* Posted June 26, 2002 I'm at work and don't have the code in front of me, but I've done this a lot at home and I will try to remember. I don't think you need any of the things Thinker mentioned, the IDE will perform the task that the two command-line tools he cited do. Dim imgBlah As Image imgBlah = Image.FromStream(Reflection.Assembly.GetExecutingAssembly.GetManifestResourceStream("mynamespace.myimage.bmp")) Try that. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
*Gurus* Thinker Posted June 26, 2002 *Gurus* Posted June 26, 2002 Good to know there are other way divil. MSDN for .net is taking some getting used to in searching. Quote Posting Guidelines
Dodgeram01 Posted June 27, 2002 Posted June 27, 2002 Good to know there are other way divil. MSDN for .net is taking some getting used to in searching. I agree. I personally don't think it's as user friendly as it could be. Quote Dodge Grab Life By The Horns
*Gurus* divil Posted June 27, 2002 *Gurus* Posted June 27, 2002 I actually find it easier. I use the Search option in the IDE and set the filter to Visual Basic and Related, then I can avoid getting results that aren't relevant (to a certain extent). Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
*Gurus* Derek Stone Posted June 27, 2002 *Gurus* Posted June 27, 2002 I find it easier as well. The whole nature of the .NET framework lends itself to a hierarchy that is easy to navigate and understand. Add that to the overall acceptable organization of MSDN in the first place as well as a search engine that often finds more than you asked for (whether this is good or bad depends on personal taste) you get a fairly nice help system. -CL Quote Posting Guidelines
*Gurus* Thinker Posted June 28, 2002 *Gurus* Posted June 28, 2002 Don't get me started on Microsoft Help 2.0. The whole xml/ namespace thing is very convoluted. I don't have any problem with the interface (although the help viewer is only a temporary one until MS releases the real help viewer). Quote Posting Guidelines
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.