Where can I store images that my extension injects into the DOM on Windows Vista?

Artie Sluka

I have a toolbar that does some direct DOM manipulation, sort of the way the IE Developer Toolbar does. Part of this DOM injection are some images that we use. Previously, we were programmatically inserting our images into the Temporary Internet Files folder, and when we created our DOM objects that needed these images the URLs pointed to the images in that folder. The problem is, that on Windows Vista it now seems that Temporary Internet Files is now considered a system folder, and I have lost the ability to write to it.

At this point, I think I have a few options but am unsure as to how to implement any of them:

1. Store the files in an accessible temporary location (using a different Special Folder, maybe ). I don't know which one, if any, I can use in Windows Vista.

2. Store the files inside my application folder, or some known place

The problem with #2 is that in order for this to work, my toolbar needs to know where it is installed. I'm not sure how to figure this out programmatically (I'm using a Deployment Project to install the toolbar).

What should I do

IECUSTOMIZER

Hi,

Store them under your application folder (add them to the Application folder in your deployment project). You should be able to determine the Application path from your application (depending upon your development language, the syntax is different)

Regards.

Artie Sluka

"You should be able to determine the Application path from your application (depending upon your development language, the syntax is different)"

I suppose that was one of my original questions: how would I go about doing that, exactly If you need to assume a language, use C#.

IECUSTOMIZER

Hi, Sorry I am not currently using C#, and don't have the time to research it for you.... Its about time that you leant how to think for yourself, and learn how to research your own answers. In this case my guess is that the application path will be a property of the application object,,, either press F1 in your C# ide or turn on context sensitive help.

Regards.

Artie Sluka

IECUSTOMIZER wrote:

Hi, Sorry I am not currently using C#, and don't have the time to research it for you.... Its about time that you leant how to think for yourself, and learn how to research your own answers. In this case my guess is that the application path will be a property of the application object,,, either press F1 in your C# ide or turn on context sensitive help. Regards.

If all you can do is insult other people's intelligence while at the same time offering up bogus answers, please stay off their threads. Do you think that all I do is put a question up here and expect other people to find it out for me I do my own homework, the fact of the matter is that there are people smarter and more experienced than I am who may be able to rattle an answer right off. Searching the MSDN library can be a real pain sometimes, especially when you're not exactly sure what you're looking for. This forum is part of my own search for an answer.

The "Application" object, in this case, is Internet Explorer, as a browser extension is hosted by the IE application. Also, the Executing Assembly path is simply the GAC, which also doesn't help me a whole lot.

At the end of the day, what I was after was the [TARGETDIR] MSI property, that I was able to insert as a registry value for a new key I created. However, this created a new and different problem, which I will put into a different thread.

cablehead

I wil be, soon, in the same boat.

Hopefully the Internet Explorer root folder can be found at setup, as I have to install a couple of C dlls there.

Artie Sluka

Well in this scenario, getting the root folder of IE should be pretty simple, as I believe Application.ExecutablePath should give you what you want (again, because IE is hosting the extension).

I'm curious though, why would you need to put your DLLs in that particular location

Artie Sluka

"Hopefully the Internet Explorer root folder can be found at setup"

Er, whoops, I guess I read that wrong, you need it at setup, not at runtime =]

That could be a bit trickier.

cablehead

The C dlls can't be put in the GAC...so they have to be in the IE folder.

Archis Gore

I'm actually facing the very same problem you are. And custom registry keys is definately not an elegant solution. But it works for now. I think the "Application" object really needs to be able to pull information about where it's "Application Path" is - even I need to deploy some images/data along with my BHO which I had trouble locating.