I need to upgrade my ajaxcontroltoolkit dll version - 3.0.20820 with the latest version 16.1
Below are couple of controls/class, for which I am facing issue:
CollapsiblePanelExtender: property used: CollapsedCssClass & ExpandedCssClass
PasswordStrength: property used: Strength
CalendarExtender: property used: CalendarMode & Enum - CalendarModeType
Q. What can we use instead of above properties as they are not available in version - 16.1?
Related
I work in a project (Upgrade from AdobeExperienceManager 6.1 to 6.3 to 6.5) where after the Jackrabbit filevault-package-maven-plugin upgrade to version 1.3.2 the following error occurs:
Package of type 'MIXED' is legacy. Use one of the other types instead! # META-INF/vault/properties.xml, validator: jackrabbit-packagetype
I searched the code, there is no single occurrence of the word "MIXED". The field properties.xml exists but does not contain any of the information mentioned in the error.
My search is stuck on this properties.xml. The information that it is legacy didn't help much since there is no documented migration path I could find on experienceleague or adobe help.
Any suggestions what to change or what exactly does this error means?
As of the [jackrabbit.apache.org][1] -documentation the error refers to the package type.
Mixed packages are a model of the past (AEM 6.3).
Means to fix it we have to separate Application /apps /libs means all the OSGi stuff and all the rest as Content.
project
- app
- src/main/content/jcr_root
- apps
- content
- etc
- libs
- META-INF
has to be split in Application-(code) my-project-package-bundle:
project
- app
- src/main/**java/com/project**/packageName
- src/main/**test/com/project**/packageName
and Content (config, templating, other data that is no java/kotlin) my-project-package-content:
project
- app
- src/main/**resources**/jcr_root
- content
- component-dialogs
- pages-config
- etc
- META-INF
I try to run the sample project from google AR Core here.
There is error in the sample code.
error CS0246: The type or namespace name 'NetworkBehaviour' could not be found (are you missing a using directive or an assembly reference?)
using GoogleARCore;
using GoogleARCore.CrossPlatform;
using UnityEngine;
using UnityEngine.Networking;
/// <summary>
/// A Controller for the Anchor object that handles hosting and resolving the Cloud Anchor.
/// </summary>
public class AnchorController : NetworkBehaviour
{
....
I am using the 2020.1.0f1 version. What can I do to fix this? It is said deprecated while the new replacement is still under development.
Deprecated but cannot be used and there is no replacement at the moment. I am stuck here.
For Unity 2020, I used Window > Package Manager and pressed the + (plus) sign:
Add Package from git URL and set it to:
com.unity.multiplayer-hlapi
and
com.unity.xr.legacyinputhelpers
as it was recommended here:
https://medium.com/#jeffreymlynch/where-are-the-missing-preview-packages-in-unity-2020-3ad0935e4193
use Window > Package Manager to install the Multiplayer HLAPI and XR Legacy Input Helpers packages.
Never mind the Multiplayer HLAPI and XR Legacy Input Helpers only available in unity version < 2020. In 2020 version, there is no option to install them both. The solution is I just downgrade the version into 2019.
I'm using aldeed:autoform#5. I also want to use yogiben's autoform-file, but I had trouble getting that to work with autoform#5 so I've used a fork by abdj:autoform-file.
Now I want to use yogiben:admin. According to the discussion on github and the latest master (https://github.com/yogiben/meteor-admin/blob/master/package.js), yogiben:admin#1.1.0 uses aldeed:autoform#4.2.2 || 5.0.0.
So why do I get this error?
C:\Webdev\koolaid>meteor add yogiben:admin#1.1.0
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint aldeed:autoform#4.2.2 is not satisfied by aldeed:autoform 5.1.2.
Constraints on package "aldeed:autoform":
* aldeed:autoform#5.0.2 <- abdj:autoform-file 0.2.0
* aldeed:autoform#4.2.2 <- yogiben:admin 1.1.0
Looks to me like Meteor is somehow picking up the wrong version from github? BTW I'm using Meteor WindowsPREVIEW#0.3.0.
How do I get all these packages to play nice together?
I have pre-generated views following the templates of the next link:
http://blogs.msdn.com/b/adonet/archive/2008/06/20/how-to-use-a-t4-template-for-view-generation.aspx
I need to improve to Entity Framework 5.0 but if I replace the schemas as following:
stringBuilder.Replace("http://schemas.microsoft.com/ado/2008/09/mapping/cs", "http://schemas.microsoft.com/ado/2009/11/mapping/cs");
stringBuilder.Replace("http://schemas.microsoft.com/ado/2008/09/edm", "http://schemas.microsoft.com/ado/2009/11/edm");
stringBuilder.Replace("http://schemas.microsoft.com/ado/2008/10/edmx","http://schemas.microsoft.com/ado/2009/11/edmx");
stringBuilder.Replace("http://schemas.microsoft.com/ado/2009/02/edm/ssdl", "http://schemas.microsoft.com/ado/2009/11/edm/ssdl");
I still having the following error:
Warning 3 The default target Entity Framework version requires the
edmx schema version 2.0.0.0 or lower. The specified schema is version
3.0.0.0. To avoid this warning specify the target Entity Framework version explicitly. You can do this by using the EdmGen.exe
command-line tool with the targetVersion option, or by including the
targetEntityFrameworkVersion parameter when calling the GenerateCode
method.
Any idea of how to solve this issue using templates?
What is the equivalent of adding /targetversion:4.5 to EdmGen using templates?
I found the solution to my problem...
There was a leading help in the following link:
http://blog.3d-logic.com/2012/05/28/entity-framework-code-first-and-pre-generated-views/
moozzyk says:
August 5, 2012 at 11:51 pm
I did see this when using Visual Studio 2012 and EF5. For now the workaround is to edit the >template. Change the line 70 from:
var errors = viewGenerator.GenerateViews(mappingItemCollection, writer).ToList();
to:
var errors = viewGenerator.GenerateViews(mappingItemCollection, writer, >EntityFrameworkVersions.Version3).ToList();
Sorry for the inconvenience.
I had to slighlty modify my code in a similar way, from:
IList errors = viewGenerator.GenerateViews(mappingItems, writer);
To:
IList errors = viewGenerator.GenerateViews(mappingItems, writer, EntityFrameworkVersions.Version3);
After that, no warning nor error whatsoever.
I've got an easy sample from the internet that works fine in the .NET 3.5 framework using System.ComponentModel.Composition.dll version v2.0.50727
I've changed the project definition and changed the target to .NET 4.0 and it works perfect.
When I replace the v2.0.50727 version of the above .dll to the latest version which is v4.0.30319 I get an error that complains during the composition of the container. The code where it break is as follows:
private void LoadPlugins() {
var catalog = new AssemblyCatalog(Assembly.GetExecutingAssembly());
var container = new CompositionContainer(catalog);
container.ExportsChanging += new EventHandler(container_ExportsChanging);
var batch = new CompositionBatch();
batch.AddPart(this);
container.Compose(batch); // throws Exception
}
And the exception is the following:
System.ComponentModel.Composition.ChangeRejectedException was unhandled
Message=The composition remains unchanged. The changes were rejected because of the following error(s): The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information.
1) More than one export was found that matches the constraint '((exportDefinition.ContractName == "MefTutorial.IPlugin") AndAlso (exportDefinition.Metadata.ContainsKey("ExportTypeIdentity") AndAlso "MefTutorial.IPlugin".Equals(exportDefinition.Metadata.get_Item("ExportTypeIdentity"))))'.
Resulting in: Cannot set import 'MefTutorial.PluginConsumer._myPlugins (ContractName="MefTutorial.IPlugin")' on part 'MefTutorial.PluginConsumer'.
Element: MefTutorial.PluginConsumer._myPlugins (ContractName="MefTutorial.IPlugin") --> MefTutorial.PluginConsumer
What do I need to do to migrate to the .NET 4.0 concerning MEF?
Could it be that another project still references the .net 3.5 version? The error message says that there are two exports of type IPlugin, which I'm quite certain of means that finds both the 3.5 and 4.0 version of the dll.
Check that only the 4.0 version of MefTutorial is referenced and/or present.
OK, I found the problem. Apparently in the previous version the notation was as mentioned in my previous comment, but in the new .NET 4.0 version the syntax for import should be:
code>
[ImportMany(typeof(IPlugin))]
internal List _myPlugins { get; set; }
Notice the use of List and ImportMany instead of IList and Import.