ImageResizer Generate a license key - imageresizer

I have purchased several licenses back in December 2013. Now, I have upgraded the ImageResizer and need to generate a key that I can use in my web.config. Previously I was using drm files and everything worked as it should.
How do I generate this key or is there any alternative?

ImageResizer v3 was the latest release in December 2013; in 2016 you're likely using ImageResizer v4. You license was valid for ImageResizer 3.X only; you would need to purchase a new license for ImageResizer v4.
See ImageResizer puts a red pixel on images?

Related

Updating .NET Core on Windows Server 2012

We just had a pen test completed and one of my servers was hit with an out of date version of .NET core. Now, in the old days of .NET Framework, I would just install the newest version on the server and call it a day. However, I'm not sure about .NET Core and what would happen if I slap v6 on there and what it will do to my existing applications. Will I be ok or do we need to update all of the applications that use that older version of .NET core when we update the version on the server?
In my opinion, you should update the old .net core version to newest version.
As far as I know for LTS .net core, MSFT will update it for each version.
Like 3.1, 5.0, 6.0, you could follow this link version to download the newest version.
But if your application is built by 2.1 and it is out of date, if you remove the 2.1 runtime, it may caused some issue.

What is the state of WiX v4?

I really feel like I shouldn't have to ask a question on SO to get basic information like this, but I can't find a reliable source anywhere.
Is WiX v4 released? In Development? In Beta? Still being designed?
Lots of people seem to already be using WiX v4, as evidenced by SO questions about it. And it has an official release page on the WiX site, without any mention of "Beta" or "Release Candidate", etc: http://wixtoolset.org/releases/v4-0-0-5205/
However, there are no released versions for v4 on GitHub: https://github.com/wixtoolset/wix4/releases
And the Wix homepage still directs you to download v3.
And one of the developer's blogs has a recent post about v4 that uses future-tense language like "will have" and "should support".
But worst of all, the current version of the WiX visual studio integration tools has templates for v4, which makes it seem like v4 is officially supported!
And when you try to build one of these templates the build error is The WiX Toolset v4 build tools must be installed ... To download WiX Toolset v4, see http://wixtoolset.org/releases/ despite the fact that http://wixtoolset.org/releases/ contains downloads exclusively for v3!
This is a crazy amount of mixed messages.
Is there something somewhere that says officially, definitively what state WiX v4 is in?
The previous answer is out dated. WiX v4 is very close to being ready and I encourage active testing of it during the RC phase.
In WiX v4, there is no installer for WiX. It's a dotnet tool you install. If your a user of Votive, Votive is no more. Instead FireGiant has a closed source but free replacement called HeatWave. This creates your .wixproj which is now an SDK style project. References to extensions are no longer DLL references but Nuget package references.
There is a tool to covnvert v3 schema to v4 schema called WiXCop. Heatwave will do this for you in a one time project by project conversion step.
WiX is no longer installed on the build server as msbuild will automatically install the SDK package references.
FireGiant reached out to be before the release and gave me a preview look. From this I was able to update my open source project IsWiX to completely support v3 or v4 using Votive or HeatWave.
All in all it's looking really good and once all the final bugs are gone I will be migrating all of my customers over to WiX v4.
WiX Toolset v4 RC2 was released on January 20, 2023. There are regular updates on the FireGiant blog that are helpful for tracking progress towards the final release. WiX v4 is now a .NET tool. This release contains many significant changes from v3.
WiX v4 does appear as a number of weekly releases which can be downloaded and installed. I've installed v4.0.0.5918, and it appears to work with the integrated Visual Studio WiX extension v4 projects, though I've not tested this extensively. The wxs project template looks identical to v3.
Considering the progress of v4, although I admit I'm quite new to this, I found a page here going back as far as end 2012!
http://robmensching.com/blog/posts/2012/12/12/the-wix-toolset-v4.0-begins/
A more recent article on WiX v4.0 and it's features can be found here
https://www.joyofsetup.com/tag/wix4/
Bug fix logs also imply v4 is being developed alongside v3, however indeed without formal confirmation, official releases, or any documentation whatsoever.
https://www.firegiant.com/blog/2015/6/2/wix-online-meeting-68-highlights/
https://www.firegiant.com/blog/2017/7/11/wix-online-meeting-130-highlights/
UPDATE
WiX v4 (preview) has just been released, for more information see the main page:
https://wixtoolset.org/docs/releasenotes/
https://wixtoolset.org/docs/intro/
I downloaded the WiX Toolset v4-rc.2 yesterday and was IMMEDIATELY disappointed. There is NO documentation giving even the slightest hint what the new XML schemas are and how they were related to or superseded v3. Also, nothing, NOTHING was done to support custom actions in .NET 6 or 7. These .NET versions have been available for several years now and Firegiant has had PLENTY of time to update all of this. I see NO ADVANTAGE whatsoever in moving to v4. Come on #robmen you are completely missing the mark on supporting this update. Do you seriously think the development community has the time to read your github v4 repository so we can discern how to use this update?? The only grace I extend to you is it is a tough job to support a product that has many users and each user's particular needs, but you decided to do this and you are failing miserably...
Actually, if this project had been open-sourced instead of taken private, the community would have advanced the functionality of this product by leaps and bounds over the years. I have been a WiX user since 2013 and it remains largely unchanged.
Case in point:
How long has .NET 5 been out?
How long has .NET 6 been out?
How long has .NET 7 been out?
.NET 3.5.1 is ridiculous...

package identity associated with this update doesn't match what's in the uploaded package

I am in the situation with the environment.
VS 2013, Update 4, CTP 3.1 Cordova.
I have been struggling for the past 1 week to publish the app to stores as it is stopping with error
"The package identity associated with this update doesn't match what's in the uploaded package".
Some gentleman has suggested to update to 2015 and ctp6 to pass through this problem.
Any alternatives that I can get here?
I tried all alternatives but could not get pass through this.
Thanks
If this is for the Windows platform (and I assume it is based on your tags), try installing this workaround plugin:
https://github.com/Chuxel/taco-tricks/tree/master/plugin-windows-package-fix
This should be resolved in VS 2015 but is an issue in VS 2013.

Hot-fix Project in Advanced Installer

I am new to Advanced Installer, since I am using a trial version, I want as much as I can about it. I have an installer, already created.
One of the files it installs is InvoicePro.exe (version 1.0.0.0). I found some bugs in that version so I built the version 1.0.0.1 in Visual Studio. Now I want to create a Hot-fix installer to replace version 1.0.0.0 with version 1.0.0.1.
Please explain me clearly!
The upgrades page from our user guide explains what you need to do. Just make sure you increase the version number for one of the 3 fields, otherwise Windows will not remove the old version, because it ignores changes in the forth field of the product version.

What are the most recent instructions on setting up a Windows 8 Monogame Project?

I'm having trouble following all of the "tutorials" and "documentation" MonoGame is providing for building a Windows 8 App. The setup is outdated because the directories don't match anymore. I installed MonoGame with the latest binary and I can access the Windows 8 template in VS 2012. I can actually use images fine and compile and do a great amount of work done, but the audio and spritefonts don't work after I've followed the importing of the xnb files from VS2010 as documented. Also, are there any Windows8 Monogame samples? I could not find one.
You might give this post by Bob Familiar a try:
http://blogs.msdn.com/b/bobfamiliar/archive/2012/08/02/windows-8-xna-and-monogame-part-2-getting-started.aspx
Just take note of some of the post's comments by Dave Voyles noting some name changes since the original post.
As for MonoGame samples for Windows 8, the third post in the series happens to have a walkthrough for creating a Tic-Tac-Toe game.
The MonoGame 3.0 Stable Released on Mon, Jan 21st which include a Windows installer that will install all the MonoGame templates for Visual Studio 2010 and Visual Studio 2012 without have to bring down the MonoGame 3.0 Branch from GitHub. Installer can be found here: http://monogame.codeplex.com/downloads/get/601094
If you need step by step instructions look at my post here: http://blogs.msdn.com/b/tarawalker/archive/2012/12/04/windows-8-game-development-using-c-xna-and-monogame-3-0-building-a-shooter-game-walkthrough-part-1-overview-installation-monogame-3-0-project-creation.aspx
This is a step by step tutorial to build a Windows 8 XNA MonoGame, which also covers .xnb files. If you need Content Processors for Cross Platform support of different textures, font, sound, etc. Look at the MonoGame wiki about Content Processing/Processors on their monogame.net site. Sorry I can't provide the link to the Content Processor info, StackOverflow won't let me post more than 2 links as a new user.