Previous Next

• 07-28-2008, 1:43 AM

  bleedow Joined on 07-28-2008, 1:35 AM Posts 5

  C# Project Deployment Reply Contact  Hi, I don't know if answere to my question isn't already on the forum... I have a project (C# Windows Form .Net 3.5) that scans the registry using MS Log Parser 2.2 - every thing works great until I deploy my project and try to run it on another computer - I found out that my Interop.MSUtil.dll must be registered in order to function properly but when I choose to register it, nothing happens - I get the same error... I don't know what I'm doing wrong or what should I do to make my app work... Maybe I'm importing it in a wrong way?? Created dll (Interop.MSUtil.dll) cannot be registered using regsvr32.exe, I get an error (somthing about DllRegisterServer). Oryginal dll created after Log Parser's installation can be registered! Please help me out with this, I would very appreciate it :( p.s Sorry for language mistakes...

• 07-28-2008, 3:10 AM

  In reply to

  qbernard Joined on 03-25-2003, 10:12 PM Malaysia Posts 2,466	Re: C# Project Deployment Reply Contact Not sure what dll is needed, but did you install LP in the targeted computer? or you don't really want to install it but like to use the dll?  Not a dev guy :) but it looks dll dependencies.. Cheers, Bernard Cheah

• 07-28-2008, 3:41 AM

  In reply to

  bleedow Joined on 07-28-2008, 1:35 AM Posts 5	Re: C# Project Deployment Reply Contact When I install Log Parser on target machine everything works great but that's not what I need. I want my app to work without Log Parser's installation...

• 07-28-2008, 4:31 AM

  In reply to

  qbernard Joined on 03-25-2003, 10:12 PM Malaysia Posts 2,466	Re: C# Project Deployment Reply Contact Ok. so when you built your dll does not highlight what dll is needed? there's only one dll in LP folder and that's logparser.dll. Cheers, Bernard Cheah

• 07-28-2008, 4:50 AM

  In reply to

  bleedow Joined on 07-28-2008, 1:35 AM Posts 5

  Re: C# Project Deployment Reply Contact I don't know if I understand you, correct me if I got something wrong Yes, there is only one dll in Log Parser's folder and it's logparser.dll I created a reference to it in my Visual Studio 2008 project and it shows as Interop.MSUtil.dll and the app works great... In Visual Studio 2008 it looks like this + MyProject (with Interop.MSUtil.dll) - SetupWizard     - Detected Dependencies        > .Net Framework        > Interop.MSUtil.dll     > Primary Output From ....  So that dll ships within my msi installation and it's being created inside my app folder.

• 07-28-2008, 5:58 AM

  In reply to

  joelangley Joined on 07-20-2008, 6:37 PM Posts 82	Re: C# Project Deployment Reply Contact Hi bleedow- Go to  sysinternals and download filemon...run filemon with a filter on your windows application/service name. See where it fails when trying to access Interop.Msutil...perhaps it is trying to look at another location.

• 07-28-2008, 5:59 AM

  In reply to

  joelangley Joined on 07-20-2008, 6:37 PM Posts 82	Re: C# Project Deployment Reply Contact Just a note...seems filemon was suggested before for the same issue...look here: http://forums.iis.net/t/1145393.aspx

• 07-28-2008, 6:51 AM

  In reply to

  bleedow Joined on 07-28-2008, 1:35 AM Posts 5

  Re: C# Project Deployment Reply Contact Small progress - now my project tree looks like this: + MyProject (with Interop.MSUtil.dll) - SetupWizard     - Detected Dependencies        > .Net Framework        > Interop.MSUtil.dll     > Primary Output From ....     > LogParser.dll And when I install msi as an administrator and run the program as an administrator every thing works great - problems retian when I install it as an administrator and try to run it as an normal user - I can see in filemon that he is looking for a dll in a folder where my oryginal project is?? That's strange... Thank you for all replies - like qbernard said the issue is connected with dll dependencies... While thred lives maybe I'll ask if there is a way to force an non Administrative Installation of MSI package??