Embedded resource

Question

4.00/5 (1 vote)

See more:

I have two projects:
1) MyProject1
2) MyProject2

Directory Structure
MyProject1
-Images
---BaseControl
------img1.gif
------img2.gif
------img3.gif
-Css
---BaseControl
------StyleSheet.css
-Controls
---BaseControl.cs - derived from CompositeControl
---Derived1.cs - derived from BaseControl
---Derived11.cs - derived from BaseControl
---Derived12.cs - derived from BaseControl

MyProject2
-Controls
---Derived4.cs - derived from BaseControl

Assembly.cs for MyProject1
NOTE: Image is set as an embedded resource

[assembly: WebResource("MyProjects1.Images.BaseControl.gif", "img/gif")]
To get the link to the WebResource, I do the following:

<br />
myImgControl.ImageUrl = this.GetImageUrl("MyProject1.Images.BaseControl.gif");<br />

This works fine with Derived1, Derived11 and Derived12 controls since the embedded resource is available to their parent. However, Derived4 control cannot find the images because the 'MyProject1.Images.BaseControl.gif' is not part of its embedded resource.

Let me know if you need anymore info.
Thanks.

Posted 12-Aug-10 3:35am

Fayu

Add a Solution

Comments

E.F. Nijboer 12-Aug-10 9:59am

Is there a question hidden somewhere?

Dr.Walt Fair, PE 3-Dec-10 22:03pm

Is there a reason why not to add the images or BaseControl to Project2?

Fayu 5-Dec-10 23:04pm

Project1 is the main redistributed assembly. Project2 is a different assembly, which contains external developers implementation of BaseControl.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)