In Visual Studio 2017 Installer Projects – Part 1 we prepared Visual Studio 2017 for creating installer projects, In this article we are creating a simple application to use as our test application that we want to build an installer.
In this series of articles we will install the Visual Studio 2017 Installer Projects and walk through creating an installer project for a simple Windows App.
Graphical interface to the Microsoft ILMerge utility. Makes it merging multiple .NET assemblies easy and hassle-free.
This document describes the ILMerge utility which merges multiple .NET assemblies into a single assembly. However, some .NET assemblies may not be able to be merged because they may contain features such as unmanaged code. I would highly recommend using peverify (the .NET Framework SDK tool) on the output of ILMerge to guarantee that the output is verifiable and will load in the .NET runtime. ILMerge is packaged as a console application. But all of its functionality is also accessible programmatically. Note that Visual Studio does allow one to add an executable as a reference, so you can write a client that uses ILMerge as a library.
When you want to release your .net application to the public as closed source you should note that Microsoft .net applications are easy to decompile and reconstruct once distributed. In this article, I intend to explore various options and explain why we settled on one particular Obfuscator that is open source. We explored a range of commercial and open source obfuscators such as ConfuserEX, ConfuserEX2, DotFuscatorCE, Obfuscar with varying levels of success.
Three additional web sites are now protected by TechnicaOne Security Sentry.
Did you know that you can view web sites in full screen mode?
Two additional web sites are now protected by TechnicaOne Security Sentry.
You are unable to set a PIN when your Windows 10 PC is connected to a domain, Your domain controller is based on Windows Server 2008 R2.
"In the Windows 10 Anniversary Update, domain joined users who connected their Microsoft Account (MSA) could roam settings and data between Windows devices. Many IT Pros told us that this functionality was not consistent with their policies for managing information owned by the organization. They did not want their PCs roaming to an individual’s personal cloud. A group policy to prevent users from connecting their MSAs did and does exist, but this setting also prevents users from easily accessing their personal Microsoft services. To address IT Pro concerns, we removed the ability for domain joined machines to roam with an MSA. Enterprises can still enable Enterprise State Roaming with Azure Active Directory."