Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Click Once Deployment & logging

Click Once Deployment & logging

Scheduled Pinned Locked Moved .NET (Core and Framework)
databasesysadminhelpquestionannouncement
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mr Brown Shoes
    wrote on last edited by
    #1

    Hi, I've recently built a smart client which uses 'click once deployment'. The program also uses the Enterprise Library for logging (among other things). Any errors that are encountered get logged to a database through a web service. If the communication with the web service or database fails a second logging policy is used which logs errors to a txt file. I recently encountered such an error that caused the program to use the second policy, but I don't know where it put the log file... Click once deployment creates a program group in the start menu for the smart client which hold the executable, not a shortcut, but the actual executable. Any idea where it installs the associated DLL's, app.config file, or potential log files? When I run the program on my development machine (not a click once deployed version) it simply creates the log file in the same directory as the executable. Thanks in Advance.

    J 1 Reply Last reply
    0
    • M Mr Brown Shoes

      Hi, I've recently built a smart client which uses 'click once deployment'. The program also uses the Enterprise Library for logging (among other things). Any errors that are encountered get logged to a database through a web service. If the communication with the web service or database fails a second logging policy is used which logs errors to a txt file. I recently encountered such an error that caused the program to use the second policy, but I don't know where it put the log file... Click once deployment creates a program group in the start menu for the smart client which hold the executable, not a shortcut, but the actual executable. Any idea where it installs the associated DLL's, app.config file, or potential log files? When I run the program on my development machine (not a click once deployed version) it simply creates the log file in the same directory as the executable. Thanks in Advance.

      J Offline
      J Offline
      JimRoss
      wrote on last edited by
      #2

      ClickOnce creates a folder for each app in your local settings folder. Mine is here: C:\Documents and Settings\\Local Settings\Apps\2.0\WCMKYTQ4.LLO\WNRQ70YJ.7OX\ Each app gets a funky folder name under there, like: \app..tion_a3097e953761587e_07d6.0003_47249f0b94b273b7\ Your exe and log files will most likely be under there. JR

      T 1 Reply Last reply
      0
      • J JimRoss

        ClickOnce creates a folder for each app in your local settings folder. Mine is here: C:\Documents and Settings\\Local Settings\Apps\2.0\WCMKYTQ4.LLO\WNRQ70YJ.7OX\ Each app gets a funky folder name under there, like: \app..tion_a3097e953761587e_07d6.0003_47249f0b94b273b7\ Your exe and log files will most likely be under there. JR

        T Offline
        T Offline
        Tailslide
        wrote on last edited by
        #3

        I'm having the same issue as the original poster and the log files are not there. I even searched the entire drive including hidden and system folders, it is not on the drive anywhere. I think there may be a compatibility problem between the enterprise library text logging and clickonce. I finally resorted to doing a custom enterprise library handler and writing it out to a file myself.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups