I have a winform application which needs to open a CSV file stored on client's PC. I am using the following code to open the CSV file and it works locally.
Process.Start(CSVPath);
However, the code does not work when I run the winform application from Citrix. Is there a way to fix this?
Related
I have tried to create an .exe file to my WPF App and SQL Server related databse with EF Core using Windows Setup Installer Project.
I included all the dll's files from /bin/Release and built it for any CPU.
The Setup Project has been created successfully and it worked on my PC as I expected.
Otherwise when I try to install the Setup File on another PC, I can't even open it up and see what's wrong.
I guess the problem comes from the database but I can't find anything helpful on the internet.
So you get the application installed, run it and nothing happens, right? Here is what you do:
Run it. Watch nothing happen
Hit the Windows key and type "Event"
When "Event Viewer" appears in the list of applications, run it
In Event Viewer, go to Windows Logs >> Application
Near the top there will probably be an error entry. It will probably be related to your application. And if you were missing a key file needed to run your application, like a DLL, the name of the file will probably be in there in the details section
Go back to your installer and add that missing file. Or if that file is part of some support package (like, say, MS Redistributable for Visual C++) then add the installer for that too.
I had this problem on how to install my vb.net application i published a while ago. After i published the vb.net project, i copied the file and tried to install to another computer but, this error was shown.
Cannot download the application. The application is missing required files. Contact application vendor for assistance.
Can anybody help me please.
I need to run this application to other computers connected to my PC as the database server.
Just-In-Time Error when running the application to another computer
This error occurs when one or more of the files listed in the application manifest cannot be found on the server. I would suggest you open the application manifest in a text editor and verify that you have uploaded all the deployment's dependent files and also check manually if the ClickOnce Install Source is correct.
If you need more information for this case then read this
I am working with a silverlight application, File.WriteAllText is giving File operation not permitted when trying to write to local desktop. Access to path exception.
This code always works on local desktop but, is giving error when code is deployed on server.
Silverlight does not have the access priveleges like u expect. If you want to add a file to your Silverlight Application at runtime, you will need to have Silverlight running Out of the Browser with Elevated priveleges. There are certain limitations to this too. You can only access files in Special Folders like My Documents, Pictures, Music etc. For more info, see this and this
I am developing a WPF application. I am accessing an admin account on a clients machine using remote desktop. When I try to run the application I am getting a xaml parse exception when the program attempts to initialise.
The strange thing is if I run the program without remote desktop on the same account it works fine.
Has anyone experienced anything like this before?
I have been porting a Winforms app to WPF and have noticed the following regarding administrative rights.
The application launches a command line exeternal app as part of its execution using 'ProcessStartInfo'. The Winforms app has no application manifest and runs the app correctly.
However the WPF version won't launch the external app correctly UNLESS I give the WPF application administrative rights. ()
I'd prefer not to do this because of the somewhat annoying UAC confirmation dialog.
I've tried adding the 'ProcessStartInfo' Verb = "runas" but that has no effect.
Does anyone know why the Winforms version is OK but the WPF version requires admin rights? FYI. The external app process a file and writes the output file into a folder in the programdata directory)
It seems that external process launched from Wpf apps don't have access to the ProgrammData folder, although the parent app does. (Yes I do actually need to write to folders within PrgrammData. I have system services that need to consume data and these services have no knowledge of users...)
By having the external app write to Environment.SpecialFolder.ApplicationData and then have the parent app move the files from Environment.SpecialFolder.ApplicationData to programdata... things work as in the Winforms apps
Writing to Program Files is not advised. If you have control over those system services, modify them to take the data from Environment.SpecialFolder.CommonApplicationData folder, this location is not user-specific and shared across the system. Then your executable will write its output to Environment.SpecialFolder.CommonApplicationData.
Where ProgramData is located? If it's under Program Files, then both your WinForms and WPF applications should have administrator rights to write to it.