I have two application configuration files in my application directory. One is named Test.config and the other is named MyApp.exe.config.
Test.config is similar to MyApp.exe.config with slight modifications.
If I execute MyApp.exe, it uses Test.config to run as certain aspects of the application is configured within these configuration files. However, if I rename MyApp.exe.config to MyApp1.exe.config, the application will not start.
If I delete Test.config, application launches correctly using settings in MyApp.exe.config. This is a .NET 3.5 WPF application.
Anyone run into this.
TIA.
Related
I have embedded tomcat container running and deploying project demo and its dependency jars in the following path:
c:\users{user}\AppData\Local\Temp\Stem_Tomcat\webapps\demo\Web-Inf\lib
Issue is, windows cleaner will delete the web-inf\lib files periodically. This happens even when the supporting Stem application is still running although the demo webpage may been closed.
How do I configure to prevent web-inf\lib*.jars from being deleted when Stem is still running ?
I was hoping to do this without having to resort to change the java.io.tmpdir location path to something else.
For context, we were originally using Jetty and windows was not able to delete the files when the Stem application was still running. I am unsure what conf changes needs to be done.
I'd need to have wpf app in a shared folder from where users could make a shortcut and run it having an opportunity to right click on the shortcut and run it also as a different user.
So, I'm wondering if I could copy all files from the bin/release folder if it could work. I did publish the app and installed it on another computer but it seems as there is no possibility to use a right click with the run as a different user. So, I did also copy bin/release files there and made a shortcut from the bin application file and the run as a different user seems as working from that shortcut on that machine. But, it might be not a right approach. The publishing and installing might not be an option further as well as it would need to go through TFS eventually where it would be copying files from a one environment to another.
I did implement it through TFS. The TFS is finally generating mainly the same files as in bin/Release when it's built via VS.
It is possible to minimize all custom java script file Manually or Automatically ?
We are using TFS for source code management , Its also possible that auto minimize Java script file by source control system or build system , when deploy code in windows Azure system or web deploy?
Note - I am not using .net application its core AngularJs application and communication done by web-api hosted on other server.
It is possible, you could integrate a build script runner like Grunt with your TFS that could minify all your javascript files. When you use Grunt you can also run it manually when developing.
I would suggest you take some time to get familiar with build script runners like Grunt to see what the possibilities are.
I have a WPF application.. I need to create 3 setups, each setup is for an environment(development, staging and production), I've put each environment configuration into App.config file of my main UI project. I need Installshield to pull the appropriate configuration file while creating the setup file.
A question: Is there a way to do it differently?
thanks,
There are several approaches you could take. Here's one:
In recent versions of InstallShield (Professional and higher editions), you can override Path Variables on a per-Release basis. If you craft your source filesystem and source path correctly, this should let you select from multiple source app.config files just by building a different release.
What is the best VS solution setup for DotNetNuke 4.8 inter-module communication development?
I currently have a solution with multiple Web Application projects in it for my DotNetNuke modules - and in each one of those have pages with the controls on them as a test harness. That all worked fine up until the point where I need the modules to start talking with each other using IModuleCommunicator and IModuleListener - but now that I'm doing inter module communication, debugging won't work out that way anymore.
I'm curious as to how other people handle this - is there a way to have your test pages mock a Nuke environment? Do you test right in a nuke website? My solution is in sourcecontrol using VSS, so I don't want to add the full nuke website as a project in my solution since that would force me to add it to source control - and I'd rather not have a full nuke site in source control.
I've been able to debug by attaching to the local IIS worker process, but that's kind of a pain. Does anyone have any suggestions as to how to ease the pain of debugging inter module communication?
Any suggestions would be greatly appreciated.
We tend to test in a development DotNetNuke site, usually just attaching to the IIS worker process for debugging (just because it's quicker than rebuilding with F5).
I think, in general, the more you're making use of what DNN provides, the less you'll be able to test outside of a DNN environment. Since IMC is a specifically DNN process, you can't have complete testing until you let DNN be the one to perform the process.
After lots of trial & error, here's what I ended up with - and seems to work well.
Created a Post-build event on the module project to copy to the local nuke site for debugging. Found under "Properties / Build Events / Post-build event command line" ... copy $(TargetDir)$(TargetName).* C:\Inetpub\wwwroot\bin* /y
Changed the web settings to start the localhost website by default. Found under "Properties / Web / Servers / Use Custom Web Server" - changed to "http://localhost/"
Created post-build events on supporting class library projects to copy file to local webserver as well. Could also have just changed the post-build event on the module project to include the other files.
Once those setting were in place, pressing F5 to run the project will start the browser and automatically attach to the IIS worker process.
Also, keep in mind that if you are running this on a machine with UAC (Vista, win 2008, win 7) you'll have to run VS as an administrator since both the copy to wwwroot and attaching to the worker process require elevated privileges.