I'm using VS 2008 and Eazfuscator latest free version and I want to upgrade to VS 2013. Eazfuscator latest free version doesn't work with VS 2013 and I took also a free obfuscator:Confuserex,is that a good one?
I found there is a Deobfuscator for that,so it is not safe?
https://github.com/UbbeLoL/ConfuserDeobfuscator
If not,a good free choice?
It is a way to integrate it with VS and automatic obfucation on build,Eazfuscator works that way.
thanks !
I chosen confuserex and I found a way to integrate it with VS
http://dev.schausberger.cc/2013/05/obfuscating-visual-studio-net-2010-code-before-creating-setup-project/
This the code found,needs to be added to .vbproj file
if $(ConfigurationName)==Release (
cd “$(TargetDir)”
“c:\path_to_\confuser Release\confuser.console.exe” “$(SolutionDir)confuserSettings.crproj”
copy /y Confused\*.*
rmdir /s /q Confused
) else (
echo “not in release mode, not obfuscating”
)
and I use:
<PropertyGroup>
<PostBuildEvent>
If $(ConfigurationName)==Release (
cd $(TargetDir)
c:\Confuser\Confuser.CLI.exe $(ProjectDir)confuserSettings.crproj
)
</PostBuildEvent>
</PropertyGroup>
confuserSettings.crproj is confuser project
the only thing I could not resolved is to use in build mode obfuscated file
i think these commands is doing that:
copy /y Confused\*.*
rmdir /s /q Confused
I don't used them because I got this error:
http://i.stack.imgur.com/jJaWH.png
how can I fix it,thanks!
It is working with these settings:
Preset: aggressive
Protection: remove antidebug
Eazfuscator works with any Visual Studio version. Support for the latest versions of the frameworks (.Net 4.5, WinRT, .Net 5) is however missing.
Related
We are slowly migrating to VS2017 and most of the project do that silently without much interference. Today started migrating a WPF project from VS2015 to VS2017. When I build the solution I get the following warning:
MSBuild auto-detection: using msbuild version '14.0' from 'C:\Program Files (x86)\MSBuild\14.0\bin'.
I googled the problem but I seem to be alone out there. I have no clue what could cause this. The .Net target is 4.5.1 but changing that to 4.6.2 make no difference. Neither does clean or remove bin and obj directories. Who has got a clue?
I encountered this problem while building from the command line after migrating from VS2017 to VS2019 for a solution containing class libraries. I found I had VS2017's version of MSBuild in my PATH environment variable - C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin. Removing that path from the environment variable and re-opening my console solved the issue.
VS2017 MSBuild autodetection takes MSBuild/v14 instead of v15 for WPF project
You can try to update the version of nuget.exe to the 4.0 and above in the .nuget folder.
Visual Studio 2017 comes with NuGet 4.0 and NuGet 4.0 Package Manager Extension is currently not available for Visual Studio 2015 (Visual Studio 2015 comes with NuGet 3.4.4, and NuGet 3.5.0 is available as an explicit download for Visual Studio 2015 as well).
According to your comment, it seems the old nuget.exe not detect the MSBuild version 15.0, so please try to update the nuget.exe to 4.0 and above in the .nuegt folder.
Besides, I found your solution that is still configured by old package restore method "MSBuild-integrated restore", which is the original Package Restore implementation and though it continues to work in many scenarios, it does not cover the full set of scenarios addressed by the other two approaches.
Automatic Package Restore is the NuGet team's recommended approach to Package Restore within Visual Studio. You can convert to use the automatic package restore. Check the following thread for details:
Nuget: Switching from "Enable Package Restore" to "Automatic Package Restore"
Hope this helps.
All of the below on Windows 7 Machines and regarding Notepad++ installation / uninstallation:
Uninstaller
When I try to uninstall using the command
if exist "C:\Program Files (x86)\Notepad++\uninstall.exe" "C:\Program Files (x86)\Notepad++\uninstall.exe" /S
there are some files left in the Notepad++ file afterward. Notepad++'s uninstaller, when run manually, prompts halfway through the uninstall asking "Do you want to keep your custom settings" and I'm thinking that the command may be choosing to answer this "Yes" by default. I'm wondering if there's an easy way to have it choose "No" here instead. If not, I can probably just delete the folder.
Installer
I'm running the installation using the 32 bit default .exe file from Notepad++ in a deployment package compiled in Lansweeper. What I'm noticing is that presently, the package executed the CMD uninstall command, but stops short of installing the new version. For reference, I've been using an installed 7.3.2 and the installer for 7.3.3 to test, so that it should uninstall the 7.3.2 and install 7.3.3 by the end of the package.
I'm wondering if the fact that there are a number of options in the Notepad++ installer could be the culprit here. If it is better to install via command line or to include some sort of configuration file I'm fine with either option, just not especially well-versed in doing them.
Notepad++ Installer requests the following during installation:
Select a language - should choose English
Choose Components - want to be able to customize selection of localization / auto complete / themes / context menu / plugins / auto update according to our requirements
Choose Components - Don't use Appdata, Allow Plugins to be loaded from Appdata, and Create Shortcut on Desktop should all remain unchecked
Run Notepad ++ - should be unchecked (checked by default)
All the other components that I can see are straightforward Next / I Agree buttons.
I'm hoping someone may be able to make helpful suggestions here as I've not had any experience with configuring silent installs with specific parameters. Notepad++ doesn't seem to have its own MSI and I won't use a third party one so some sort of batch or configuration file or flagging options in cmd if possible are the preferable options.
Please let me know if there's any additional information I can provide that may be helpful.
Thank you in advance.
If you just need to update to the latest version. It is quite simple. Run the newest installer again and it will automatically update older versions.
See
Silent Install Notepad++
I'm using the command:
start /wait npp.7.2.Installer.x64.exe /S
Didn't show any interface during silent installation.
Notepad kicks a secondary process that doesn't finish until success is evaluated.
try:
"%ProgramFiles(x86)%\Notepad++\uninstall.exe" /S
timeout 5
We are looking to create responsive skin for a Dotnetnuke 7 installation
We have done this before by just writing the code and using winless to compile it and uploading the css.
This worked ok but having recently made an umbraco site with support for .less files (using uless) the process was a lot smoother
I have tried to research the subject but can't dig up anything more recent that this
http://www.xram.net/blog/2010/6/9/integrating-dotless-dynamic-css-with-dotnetnuke/
Which is from 2010, so several versions of dnn ago
Has anyone got something like this working in a recent version?
If so does it break after upgrades
I would even consider using a 3rd party module if there is one available but i couldn't find one
We use less with our DNN implementation. We use the dotless.compiler.exe and a simple batch file to compile the less and copy it to the desired location. So our modules/portals deal with the compiled css but our skins folder contains the less. Batch file looks something like this:
#set svnRootDir=C:\Projects\MyMantra
#set deployDir=D:\Web\Public\BrandSites\Website\Portals\_default\Skins
%svnRootDir%\Scripts\Packaging\dotless.compiler.exe %svnRootDir%\MG\Skins\Skins\Breakfree\css\*.less
robocopy %svnRootDir%\MG\Skins\Skins\Breakfree\ %deployDir%\Breakfree\ /s /XF *.less *.htm *.html
NOTE: robocopy /s - Copy Subdirectories, but not empty ones and /XF - eXclude Files matching given names/paths/wildcards.
I prefer this over what is mentioned in that blog post since it doesn't mean a core change and you keep the DNN core vanilla so upgrades don't cause any problems.
I have two MSI installers,BasicInstaller.msi and updateInstaller.msi.As name suggests,the updateInstaller.msi is a updated version(with some new files added) of basic installer.I have installed Basic installer in UI mode where i have mentioned the installation path as "D:/MSIApp".
I am installing the updateInstaller.msi in silent mode using msiexec.cmd(this goes into a bat file) that overwrites the files and registry entries created by BasicInstaller.msi. I am able to install it using the below command
msiexec /i updateInstaller.msi /qn TARGETDIR=D:/MSIApp
Now,i am looking for logic where in the installated path of basicInstaller is picked up and updateInstaller is installed at the same location.In short,i want to avoid TARGERDIR switch hard coding.
If i don't specify TARGETDIR in the msiexec,the updateInstaller is installed at the default "C:/programfiles/..." location.
Could some one help me with the possible solution options.Any help appreciated.
This is usually accomplished by having the installer lay down an InstallPath (or similarly named) registry entry. Subsequent installers can read the entry and use it as their installation path.
See this page for an example.
i am searching for hours now, a way that could allow me to install (optionally) a custom firefox extension along with my software installation package.. i can't find anything useful tho. Tried the registry method, the -install-global-extension method, the "Copy to extensions path" method... but nothing seems to work.
Any ideas on how to let the user chose if he wants to install my extension after my package install is finished?
You have this tagged "batch" so I'm assuming you are looking for a way to install extensions from the command line using batch format.
What is the output if you were to use something like this?
for %%e in ("path to extensions\*.xpi") do "firefox.exe" -install-global-extension "%%e"
I have an Nsis installer that in one of its steps copies a Firefox extension to the extensions directory. That works for every Firefox version from 3.0 to 4.0.
First it finds out which is the directory for the default profile, following this pattern: %APPDATA%\Mozilla\Firefox\Profiles*.default. Once profile name is determined (for example "4v3vxq80"), it copies the extension to %APPDATA%\Mozilla\Firefox\Profiles\$1\extensions (where $1 is the profile name).
I think the key is that all these steps are performed when Firefox is not running (I check for a running firefox.exe at the beginning).
Let me know if you want the nsis code that does the trick.