|
I'm using a Visual Studio 2017 Setup project to install a Windows Service.
The Application folder's DefaultLocation is set to "[ProgramFilesFolder][Manufacturer][ProductName]"
The Manufacturer property is set to "My Company". The ProductName property is set to "My Product".
When I run this Installer, it dumps all files into the root of c:. The Manufacturer and Product folders are not created.
Anyone have any idea what's wrong?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
What is a Visual Studio 2017 Setup project?
Are you talking about InstallShield Limited Edition?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
|
Is there information about an example of a tiff file display for .net core?
|
|
|
|
|
Possibly, and Google will know where to find it.
|
|
|
|
|
I couldnt find it 
|
|
|
|
|
Maybe there is no such product.
|
|
|
|
|
Ignore the server; use a Javascript solution instead:
https://github.com/seikichi/tiff.js[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I'm trying to install a .net Windows Service on a PC with WIn 10 running. Windows Defender is running, and this installation has to be done without turning it off. The setup will be called from another setup. We CAN addd the setup.exe to the list of allowed apps.
So, I've tried creating a VS installer Project by following this. It works in stat it sees to install, but the service istself doesn't appear in the Servics dialog.
So, if I manually turn on Real-Time Protection in Windows Defender and use InstallUtil, it installs fine. But with Real-Time Protection on it fails, so I'm trying to get the Installer to work.
I'm open to suggestions here.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Have your main installer call InstallUtil to install the service.
Never mind, I didn't read carefully enough.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Kevin Marois wrote: if I manually turn on Real-Time Protection ... it installs fine. But with Real-Time Protection on it fails
Was that first "on" meant to be an "off"?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I built a project payroll management system with vb 2012, MS Access 200 db, Crystal Report XI. In report section when I want to see a employee salary detail record for more than 2 year the report showing month year field not arranged like March_2019 than November_2016, January_2018 want to short by November_2016 than January_2018, March_2019. My access db table contain Month_Year format. So please help me to short the report.
|
|
|
|
|
NSE India wrote: So please help me to short the report.
Do you mean "sort?"
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Assuming you're storing the data in the correct data type - ie: as a date - then you need to sort by the raw date value before you format it. Otherwise, it will be sorted alphabetically, and "August 2019" will come before "January 2010".
If you're storing the data as a string instead of a date, then you don't stand a chance. Fix the data storage first.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I have a project that is referencing Newtonsoft.Json V11, but, some other assembly in my solution is is referencing Newtonsoft.Json V6.
I beleive that some 3rd party assembly is the culprit, but how do I find it? is there a tool to list all assemblies and their dependancies?
Thanks
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
|
Hello , I am currently working on a project which requires the use of a custom dll for authentication.
This dll is registered (so they told me) in the GAC of both the Production and Test environments.
The company policies state that you "shouldn't include the dll reference in your application's web.config file", that is, you shouldn't have something like :
<add assembly="" ....="" mydll=""> etc.
in your web.config, at least for this dll I am talking about. They say, since it's registered in the GAC, the application will load it anyway.
The problem is , if you don't add the assemby reference in your web .config , the application is not going to find it , no matter what they say.
Since I am sure the dll is actually registered in the GAC, my question is :
shouldn't the application be able to load the dll anyway , no matter if you add the reference in the web.config or not ?
I was convinced that, adding the reference to the project, the dll 's GAC location would be stored in the application's assembly so that the application itself would be able to find the assembly in the GAC , no matter what the working system is , given that the dll is actually registered in the working system's GAC .
But I must be wrong.
What is the real way it works ?
Thanks
Leo
|
|
|
|
|
Global Assembly Cache | Microsoft Docs[^]
MSDN wrote: The Global Assembly Cache stores assemblies specifically designated to be shared by several applications on the computer.
tiwal wrote: I was convinced that, adding the reference to the project, the dll 's GAC location would be stored
The GAC location doesn't need to be stored; it is managed by the .NET environment.
You will still need to add a reference to the dll. The difference is that you no longer have to copy the dll to the local output folder (which VS does for you, usually), but that the app will use the one that is registered in the GAC.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Hi Eddy thanks for answering.
You mean that I still need the <add assembly="" ...=""> tag in the application's web.config ?
Doesn't the application's assembly contain a reference itself ?
The production cluster specialists in my company scolded me for putting the <add assembly="" ..=""> tag in the web. config, but then I showed them how it would behave without it, and they were baffled ....
|
|
|
|
|
tiwal wrote: You mean that I still need the <add assembly="" ...=""> tag in the application's web.config ?
Doesn't the application's assembly contain a reference itself ?
It does for WinForms; the references are part of the project-file, and compiled into the assembly. I'd assume ASP.NET does the same.
How the Runtime Locates Assemblies | Microsoft Docs[^] seems to suggest that the config-files are the first location where the runtime looks.
tiwal wrote: The production cluster specialists in my company scolded me for putting the <add assembly="" ..=""> tag in the web. config
Why? Any specific reason why it is considered "bad"?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: Why? Any specific reason why it is considered "bad"?
Well I assume they, like me, were expecting everything to work fine without the need to add the specified tags to the web.config ... appearently, we both were wrong....
|
|
|
|
|
I want to print a log whenever an exception is thrown by try-catch block through out whole application.
|
|
|
|
|
What type of application? WPF? WinForms? Xamarin? ASP.NET?
This space for rent
|
|
|
|
|
A try..catch block doesn't throw exceptions; it's used to handle them.
If you want to log all unhandled exceptions, then the code you need will vary depending on what type of application you're writing. You could start with the AppDomain.UnhandledException event[^] and the TaskScheduler.UnobservedTaskException event[^].
If you really want to log every exception, even those which are handled, then you'll need to subscribe to the AppDomain.FirstChanceException event[^]. NB: This will generate a lot of noise. You will be logging every exception thrown in any code, including .NET itself, regardless of whether or not it's handled.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: the AppDomain.FirstChanceException event[^]. NB: This will generate a lot of noise.
Thank you for that!
Would you happen to know if using this event would cause a significant slowdown, even if the code in the event handler is trivial?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
