By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
460,023 Members | 1,297 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 460,023 IT Pros & Developers. It's quick & easy.

Conflict between C# and iTunes?

P: 6
This is not a post for asking something.. is more like a remark..
But I would really appreciate some explanations if possible..

I am now building an application with C# from MS Visual Studio 2005. I also listened some music with iTunes When compiling the application I got no errors, but on running this simply does nothing and I get a nice error :)

here is the error:
"Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang."

First, I didn't know what to do, because I've ran the same application 30 minutes ago and worked perfectly:)

The error shows in Program.cs file.. not even in my classes.

So I reboot.. and after the app works again.
Of course, opened iTunes also. The app crashes in the same way as before.
Just closing iTunes and able to eork with my app.

// of course, I tested this with other C# apps before writing this post.

I don't know whether iTunes is responsible for this or the conflict is between win and iTunes. If anybody knows more about this please share some knowledge.
// I found this error only on my compuyer, didn't tested on other systems yet.

I run Microsoft Windows XP Professional SP2, on intel platform.

thanks for reading all this post and please share some info if possible.

Cheers, Maj
Sep 13 '07 #1
Share this Question
Share on Google+
2 Replies

Shashi Sadasivan
Expert 100+
P: 1,435
I googles "visual studio itunes" and the very first link says it all.

PS - For some reason i avoided playing iTunes while working on visual studio (memory intensive) rather played my iPod :D, Alarmed at this bug with Mac
Sep 13 '07 #2

P: 6

Thanks for the info, I was really curious what happened there because I got this error yesterday for the first time [before i was using winamp and no problem].

Sep 14 '07 #3

Post your reply

Sign in to post your reply or Sign up for a free account.