I have been playing around with the new StateMachine workflow that has been added to Windows Workflow as part of Platform Update 1 (see also). I now want to look at installing what I've created and therefore need to make sure my bootstrapper is up-to-date. In the future, I will be moving to WIX but right now, for the purposes of prototyping, I'm just using a regular Setup and Deployment project and its bootstrap support.
The list of standard pre-requisites does not include the PU1 as an option. Therefore, how can I add support for it?
Update
I found this answer on StackOverflow regarding custom prerequisites, which led me to this article on MSDN, which led me to creating my own pre-requisite. However, I got a new error about mismatched framework requirements. I suspect I need to pick apart the multi-targeting support and the existing .NET framework prerequisite package to see how to make a new prerequisite that will work correctly.
I've had a stab at creating my own bootstrapper packages for this. The results are here to download. Note that these are entirely untested and provided as-is - use at your own risk. However, feedback is welcome. Hopefully Microsoft will provide an official solution.
See How to detect if the .NET Framework Platform Update 1 is installed
is the Microsoft .NET Framework 4 Platform Update 1 - Runtime Update (KB2478063) what you are looking for? See here for the download.
Related
Environment(s) DNN 9.10.2 / 2sic_2SexyContent_14.07.04 Install / Oqtane 3.1.4
I've modified the 2sxc Blog module 4 to be a book reading log.
I've created 608 entries and wish to export/import to Oqtane 3.1.4 site.
I attempted the export from 2sxc without noting the module version and when importing the data I get the following error:
Could not import the app / package: Sequence contains more than one matching element.
This is similar to https://github.com/2sic/2sxc/issues/460.
I've even installed 2sxc on another vanilla DNN 9.10.2 site and attempted the import on that (with the latest version of 2sxc 14.7.4 and get the same error.
I've seen in the Github issue noted above you could analyze the import process in your development environment? If so I'd be happy to send you the import zip file created from the App Export feature in 2sxc App Settings.
I have looked pretty deeply for any guidance on configuring the development environment for 2sxc and haven't been able to find anything. Also does anyone have good guidance on how to set up a development environment for the 2sxc modules? Would be great to include steps to set this up in Oqtane as I am moving all of my development energy moving forward to Oqtane module development - Oqtane is the next logical step for DNN Developers.
And also goes without saying that 2sxc is one of the best modules ever for DNN and offers a migration path away from DNN when you find that time coming. I've just gotten my Epiphany moment with Oqtane 3.1.4 realizing it is about at the same point DNN 2.1.2 was - a mature, extensible framework from which to build your .NET Core apps with.
It's great to hear others are experimenting with Oqtane - awesome!
Your first step should be to check the insights log on the API call that does the import. It will probably show you exactly where it failed.
My guess is that it has to do with languages which are enabled / disabled differently in Dnn and Oqtane.
I am working on a project in MixedReality using mainly MRTK and its features. I found out that MRTK can use QR codes to read data, and I wanted to use it and try multiples ideas.
The problem is that, currently, is seems any QR feature is nonexistent in my project.
I Installed the NuGet package Microsoft.MixedReality.QR and its corresponding Microsoft.VCRTForwarders.14 package, as indicated in
https://localjoost.github.io/Reading-QR-codes-with-an-MRTK2-Extension-Service/
But anything I try in code, from my project, will tell me in the console window that the namespace could not be found, and all cascading items (properties, classes, functions) could not be found either, none of them.
It is weird since everything should be installed and up to date ( I verified this directly in Visual Studio and everything is there).
Any kind of help would be much appreciated, thanks !
For Unity projects, you need to import NuGet for Unity to install Mixed Reality QR NuGet package. Meanwhile the tutorial you are referring is not an official document. Some types/classes are defined by the author and are not included in Microsoft.MixedReality.QR namespace.
Please refer to the new QR sample on https://github.com/yl-msft/QRTracking and all the C# API references are listed on QR Code tracking API reference
I've been developing an app that uses QRcode on the hololens as well. I ran into that issue before, and the console seemed to throw that error for me because I was using the wrong version of the MRTK services in the Microsoft Mixed Reality Feature Tool. I would recommend using version 2.6.1 for all your services. Do you by any chance have a problem where "QR tracking is not supported" for the Unity Project you are building?
Is there anyway i can check if .NET 2.0 is installed without any errors?
The answer here led me seriously astray... i found microsoft's own documentation: .NET Framework 2.0 Redistributable Package Reference: Detecting Installed .NET Framework 2.0
This documentation states:
The Setup.exe bootstrapper should use the following registry key to detect the .NET Framework version 2.0.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727
It then verifies the existence of the entry value:
Install (DWORD value = 1)
Note The same registry key will be checked for all versions of Dotnetfx.exe regardless of language. Therefore, if you want to display dialogs in a specific language you should use the corresponding version of Dotnetfx.exe. You do not need to make any changes to the settings.ini file when deciding which version of Dotnetfx.exe to use.
works like a charm... i realize this question and answer is 2 years old or more... but i got here from a search engine, and this is here for the next person who does the same... hope this helps -ck
This blog post describes two options for checking for a .NET installation, as well as retrieving versioning information.
The second option (using CorBindToRuntime) will fail if the .NET installation cannot be loaded. This might help you determine if there are any errors in the install - or at least whether the framework loads properly.
If you're using ClickOnce as your publishing method, you can click on the "Prerequisites" button in the "Publish" tab of the project's properties and check the box for ".Net Framework 2.0". This will make sure that framework is installed before the program installs, and can fetch and install the framework if necessary, too.
In regular VS Setup Projects, right-click on the setup project, chose View->Launch Conditions and add it as a condition. Visual Studio should have added one for you that matches the target platform of the project.
Where can I find information about upgrading Magento Enterprise 1.7. to the latest 1.9. ?
There's no such documentation.
Your general approach:
1. Close production server
2. Backup all DBs and Magento installation
3. Turn off all your custom extensions and themes
4. Delete from HDD: core Magento modules, their layouts, all standard themes and cache.
5. Get 1.9 EE, copy it over your installation
6. Request Magento through http
7. Walk at your site, notice errors and warnings, fix them
8. Check documentation and update for your theme, whether it supports EE 1.9. Turn it on if it supports, otherwise you'll need another theme.
9. Check documentation and updates for all your custom extensions - whether they support 1.9. Turn them on - one by one.
You won't have any problem with upgrading all core DB data - it's made automatically.
You'll have problems with your custom theme, as you'll need new version with support for 1.9. And you'll need to check your custom extensions and upgrade their source and DB data to fit 1.9.
Generally all Magento upgrades work by running the updated code with the old database. The differences will be detected and incorporated automatically on the next page request. Magento keeps track of every module's version number for this reason.
Because there is a chance some modification will break it is best to do this on a new (temporary) site then add the modifications back in gradually. That way the old site is still active and uninterrupted.
I think there is no official documentation. The best way is to figure out what core functionality is used in your customizations and after that look at theirs realization in new version: does it changed or not.
To know what was changed in new version you could check changeslist
I have been having a real hard time getting API Tooling to work in Eclipse 3.4.2. It keeps telling me:
The minor version should be incremented in version 3.4.0.qualifier, since new APIs have been added since version 3.4.0.40001
That being said, I have generated the plugins that are used for the baseline from the exact same code that it is being analyzed against. The API Tools docs say that it compares the current code against the baseline to see if there are any differences. I can't see how there could be differences if the built version is built from the current code.
The way that I tested it:
Create a new eclipse workspace
Create a new Plug-in Project with API Analysis turned on
Add a simple class to that plugin and export the package with that class in it
Build/Export that plugin to some location on your hard drive
Set the workspace baseline to that location and do a full build
You get an error for the project in your problems view.
Thanks,
-One very perplexed user
Looks like this is something that got fixed in 3.5. Too bad my company doesn't want us using 3.5 in case there are any incompatibility issues. (there were 3.3 to 3.4)
My recommendation to anyone who wants to do Eclipse API Analysis is to use 3.5.
First off, I apologize for jumping on a thread late after its "active time" but I am currently running into this exact situation, but with Eclipse Helios 3.6.
From your answer, you noted that something was fixed in 3.5. Are you aware of what this exact fix was AND if you have yet been able to verify that it is working under Eclipse Helios 3.6?
I would really like to have PDE API tooling working but I'm nearing my time allowed on this effort and need to move forward onto some pending tasks.
Thanks!
EDIT: I would have posted this in a followup link but did not see any such links available.