clickonce

Where can I write my log4net log file to under ClickOnce?

守給你的承諾、 提交于 2019-11-30 09:21:22
When I run my application locally it writes my log4net log to the location I've configured (i.e., <file value="${LOCALAPPDATA}\TEST\Logs\debug.log" /> ) without a problem. However, when I deploy my application via ClickOnce, the log file is not being written. I know ClickOnce applications are limited in terms of where they can write to, but I was under the impression that LOCALAPPDATA (e.g., C:\Users\me\AppData\Local) was fair game. Any ideas? Isolated Storage. With ClickOnce, the folder rules are somewhat different than for regular Windows apps. The data folder, where ClickOnce content files

Why does my .net application require full trust?

点点圈 提交于 2019-11-30 08:47:59
I've developed a .net 3.0 application, which is deployed using clickonce. I'd like to move from full trust to partial trust to ease deployment. I've tried the "Calculate Permissions" tool in the "Security" tab of my project under visual studio, and the answer is quite clear : --------------------------- Microsoft Visual Studio --------------------------- This application requires full trust to run correctly. However, I've not been able to figure out why full trust is required. I've tried to change the security settings to "partial trust", but the application raises a SecurityException

Msbuild command line argument at project-level not solution-level for changing AssemblyName

﹥>﹥吖頭↗ 提交于 2019-11-30 08:44:10
问题 Is there any way to specify a command line argument for msbuild that will apply only to one project (i.e. project-level not solution-level), when building a multi-project solution? The reason I ask is because I want to enable side-by-side installs of a click-once deployment. Let me give an example: 1) This works MSBuild "C:\Dev\MyProj\MyProj.Shell\MyProj.Shell.csproj" /p:SkipInvalidConfigurations=true /target:publish /p:OutputPath="C:\Dev\Temp\" /p:ApplicationVersion=1.2.3.4 /p:ProductName=

“File has a different computed hash than specified in manifest” error when signing the EXE

夙愿已清 提交于 2019-11-30 08:38:53
问题 My ClickOnce installation fails with an error: File, WindowsFormsProject.exe, has a different computed hash than specified in manifest. I use MSBuild to generate ClickOnce deployment package. The relevant line from the build script: <MSBuild Targets="Publish" Projects="WindowsFormsProject.csproj" ContinueOnError="false" /> The WindowsFormsProject.csproj has a Post-Build step that signs the executable, as follows: signtool sign /a $(ProjectDir)\obj\$(PlatformName)\$(ConfigurationName)\$

Unable to install or run the application: Click Once

主宰稳场 提交于 2019-11-30 07:59:20
I published my .net application using ClickOnce, and all my users get the following error message on trying to open the program: "Unable to install or run the application. The application requires that assembly Telerik.Windows.Data Version 2012.1.215.40 be installed in the Global Assembly Cache (GAC) first". The version I actually use in my application is NEWER than the one mentioned in the error message. I also don't have this problem on my machine which I use to develop the application. I wonder why it is looking for the older version of the dll. I can't find where it is referenced by my

Do not overwrite settings.settings file with clickonce

旧时模样 提交于 2019-11-30 07:42:41
问题 At first I had some userdefined settings stored in my app.config file, under appSettings. These are properties the user can change during runtime. The first problem I've got is when I deploy my application with ClickOnce it overwrites the app.config file and the user has lost his personal settings. Then I moved the properties to the settings.settings file (= usersettings section in app.config) as I found on the internet that this section doesn't get overwritten when deploying with ClickOnce.

How can I get MSBuild to increment the ClickOnce publish revision version number on a build server?

牧云@^-^@ 提交于 2019-11-30 07:30:54
We have an NAnt script that checks out from CVS and then runs MSBuild to publish the application. The problem is we have to remember to always increment the version in Visual Studio. We have the option to auto increment this on publish, but this gets wiped on the next checkout and I would rather not have to get the build script to check in the project file. Is there a simple way to do this? KyleMit Updating the MinimumRequiredVersion Automatically Introduction to Project Editor In Solution Explorer, right click on your project and select unload project. Once the project has become unavailable,

deploying a database and application with ClickOnce

不羁岁月 提交于 2019-11-30 06:48:17
问题 I am new to ClickOnce. I created a WinForms application using C# and SQL Server Express. Currently my database is located in the mssql data folder. My connection string is located in an app.config file. <add name="default" providerName="System.Data.SqlClient" connectionString="Server=localhost\SQLEXPRESS;Database=DBase;Trusted_Connection=True;" /> How do I include my database file for it to deploy with the application? To which folder will the database be deployed and will my connection

“Manifest XML signature is not valid” on client machine but works fine on developer computer

心已入冬 提交于 2019-11-30 06:31:01
问题 At work we had a ClickOnce application that, when the client would try to install, was throwing the exception: Exception reading manifest from file:/FILEPATH: the manifest may not be valid or the file could not be opened. Manifest XML signature is not valid. SignatureDescription could not be created for the signature algorithm supplied. To solve this, we ended up using another certificate file, and it worked fine (resigned the manifest). But we can not understand why it would work to install

Installing a ClickOnce application from two different locations

天大地大妈咪最大 提交于 2019-11-30 05:47:24
问题 I have a Windows Forms application developed using C# in .NET framework 3.5, Service pack 1. The application can be published based on the development database as well as the production database. I am using MSBuild community tasks to publish my application. I do not face any problems while publishing the application to different location, namely a development location and a production location. Issue: After installing the development application into my machine, I am unable to install the