Since CodedUI does not support Infragistics winforms by default, a hotfix has to be installed which imports a specific assembly enabling codedUI to work with infragistics controls. This hotfix works with vs2010 pretty fine, but not actually with vs2012. Their site says that this hotfix should work with vs2012 but I just can't install this hotfix because of a compatibility issue. When I try to install it, this is the error message I get:
KB2696646 does not apply, or is blocked by another condition on your computer. Please see http://go.microsoft.com/fwlink/?LinkId=225649 for more details.
Is there a way to get the assembly without installing this hotfix?
Or could someone just share it? This is the one I need: Infragistics4.Win.CodedUITest.UIA.VS11.v12.2.dl
Thanks
Please take a look at : http://www.infragistics.com/community/forums/p/79850/402667.aspx#402667 for more details. Also there you could find mentioned assembly.
Related
I'm using WinRT C# application and after a Windows update 20H2 (framework: 528372), the syncfusion Scheduler component stopped working and crashes the application. On Windows 1909 (framework: 528040) it works correctly
The error: Cannot create instance of type 'Syncfusion.UI.Xaml.Schedule.ScheduleAppointmentEditor'
I updated the libaries to a newer version which didn't solve my issue.
I currently have two versions of the same application
WinRT
UWP
The UWP works fine on 20H2 Windows versions and both UWP and WinRT apps have the same libaries for the syncfusion.
Any workaround that I can put in place to make it work again on version 20H2?
Regarding Cannot create instance of type 'Syncfusion.UI.Xaml.Schedule.ScheduleAppointmentEditor
The reported issue has been fixed and included in the patch which can be download from the below links.
Recommended approach - exe will perform automatic configuration.
Please find the patch setup from below location:
Patch link:
https://syncfusion.com/Installs/support/patch/14.4.0.15/1015043/F168937/SyncfusionPatch_14.4.0.15_1015043_9272021085339206_F168937.exe
Please find the patch assemblies alone from below location:
Assemblies Link: https://syncfusion.com/Installs/support/patch/14.4.0.15/1015043/F168937/SyncfusionPatch_14.4.0.15_1015043_9272021085339206_F168937.zip
Nuget link: https://syncfusion.com/Installs/support/patch/14.4.0.15/1015043/F168937/SyncfusionNuget_14.4.0.15_1015043_9272021085339206_F168937.zip
Disclaimer:
Please note that we have created this patch for version 14.4.0.15 specifically to resolve the issue reported in this incident.
Syncfusion gave an updated library with the fix. Issue Resolved
Heres the link, version 14.4.0.15 but this is specific to this issue as i could read : https://www.syncfusion.com/forums/168937/cannot-create-instance-of-type-syncfusion-ui-xaml-schedule-scheduleappointmenteditor
In my VS2012 project with Internet Explorer 10 installed if I add a reference by going to the COM references and choose MSHTML then it gives me the version that is installed in the GAC which is an old 7.0.3300.0. If I actually look in system32 or sysWOW64 then the .dll tlb version is a much much newer version.
How should I develop against the newer version?
If I understand it correctly mshtml is installed with Internet Explorer so if my deployment machines have IE10 then I should have no problems right?
Can anyone guess why the GAC has the old version in it? I have just check 2 other Win 7 installs and it is the same. GAC is 7.0.3300.0 but elsewhere it matches the IE version.
EDIT: The other Win 7 machines all have VS installed. I just looked on another Win 7 and there is nothing in the GAC. Is VS2012 installing this in the GAC?
Update after Comment
It appears that there are a few questions about this. this reference from the comment also this question which Hans was also involved in. I also found this forum thread as well on the topic.
I still down know what I should be doing, but I can certainly simply follow like a sheep the instructions. I suppose I need to create a PIA that will allow me to call the newer methods (This fixes VS), but understand that if this code is used on a PC that does not have the compatible MSHTML / IE version then it will crash. (Same as the Office PIA and if you call for example an office 2013 method that does not exist on an Office 2010 installation.).
In my question I have linked to what are probably seen as the more correct answers to this issue.
If someone is looking for a quick and dirty solution then use late binding. I will explain specifically in my case what this means.
Dim div as HTMLDivElement
'make div something
div.getElementsByClassName 'this was not working!!!
This would not compile as the reference that Visual Studio is using is an old version.
So instead of follow the above because I only needed this a couple of times I changed the code to this.
Dim div as Object
'make div something
div.getElementsByClassName
Now Visual Studio will not have a problem with it. The problem you do face is that the final end user must have at lease a version of MSHTML (which is installed with Internet Explorer) that has this method or higher.
I hope this helps people who are still trying to work out what PIA's are and how they work in Visual Studio and MS environments.
I am attempting to convert the Microsoft.Health C# class library that is installed as part of the HealthVault SDK, using instructions provided here. After following these instructions, I get the following error when attempting to load the project into Visual Studio 2013.
"The project is targeting frameworks hat are either not installed or
are included as part of future updates to Visual Studio. See
http://go.microsoft.com/fwlink/?LinkId=287985"
Visiting the link takes me to .NET SDKs and Downloads. Once there, I have no clue on what needs to be done.
I do realize that one will have to leverage the Portable Class Library Contrib project to fill in some missing bits, especially code related to System.Security. This, I will deal with later.
Any one run into a similar problem?
Maybe so late but for those who have the same problem.
I had the same error in a project which was working perfect before updating VS2013 and finally after 3 hours looking for the source of the error I found that the error is about TargetFrameworkProfile.
In my case I sloved it like so:
Right click in the unloaded project in your solution and click Edit.
Find the TargetFrameworkProfile tag and set it as below:
<TargetFrameworkProfile>Profile78</TargetFrameworkProfile>
At a guess, this is because you need to specify the TargetFrameworkVersion and TargetFrameworkProfile properties in the project file. Compare the .csproj you are trying to create to a newly created PCL project file, and make sure that everything that's not specific to your project matches.
I ran into the same issue and got it resolved by installing the latest Visual Studio Update
I recently acquired XMLSpy 2013 and was naturally excited to see there was a Visual Studio integration package. I'm running VS 2012, but nowhere on Altova's download page does it mention compatibility requirements/limitations.
So I followed the steps on the Altova download site (basically just run the package and you're done). Nothing changed in VS. So I decided to download the 1326 page PDF manual for XMLSpy to see if there was some extra help in there:
http://www.altova.com/documents/XMLSpyPro.pdf
On page 490, it mentions going into your VS/Common7/IDE directory and running devenv.exe /setup which I did. After that, again, nothing changed.
Has anyone had any success with getting this integration package to work? I can find almost no information by searching the web.
I actually created a support ticket with Altova for the issue as well, but thought I'd try here for some first hand experiences.
Whelp, Altova support responded to my ticket. The answer is, since Visual Studio is a 32-bit only application, XMLSpy integration will not work when running the 64-bit version of XMLSpy/XMLSpy integration package.
This is despite the fact that both a 64-bit version of XMLSpy AND a 64-bit version of the Visual Studio Integration package exist side-by-side on the download page (as of writing this answer). I have a feeling that it might only exist for the Eclipse integration.
http://www.altova.com/download/xmlspy.html
Once I installed the 32-bit versions of XMLSpy/Integration package, it all worked as promised. I hope this helps someone in the future at least.
I am trying to compile the vNext branch of MvvmCross on a Mac to try & start doing some iOS development using PCL's & MvvMCross.
I have spent a couple of days on this now but appear to be going in circles... being somewhat new to both C# & the Mac.
I have installed MonoDevelop 3.1.1 as recently referred to on #slodge's blog.
I have updated the targets file as per this reference https://files.xamarin.com/~jeff/Microsoft.Portable.CSharp.targets
I have downloaded the vNext branch from GitHub.
I have loaded the mvvmcross_all.sln in MonoDevelop however building it using the Debug|iPhone Simulator profile gives me 3 errors.
I have not been able to work out how to fix the references errors as for example appear in CrossUI.Core, ie references to
System
System.Core
System.Net
etc
Each of these lines has an error of Assembly not available for .NetPortable 4.0 Profile1 Profile (in Mono 2.10.9)
I realise its all a moving target but its obviously possible to get it to compile.
Any suggestions as to what I may have missed would be appreciated.
TIA,
Andreas
Thanks Andreas
In the version referenced in the blog at http://slodge.blogspot.co.uk/2013/02/a-patched-monodevelop-for-pcls.html, it appears that MonoDevelop reports that CrossUI is missing its references - but it still compiles. See this screenshot from my Mac - solution explorer reports problems but 'rebuild all' on CrossUI succeeds.
If you get problems with building, please do report the build output and I'll try to help.
Note that the patched version of MonoDevelop also still has other problems - e.g. syntax highlighting and intellisense issues- MonoTouch: creating multiplatform apps using Portable Class Libraries
Alternatively, there are some iOS/Mac friendly binaries on SkyDrive - http://slodge.blogspot.co.uk/p/mvvmcross-binaries_7.html
The schedule for 'proper' support of Portable Class Libraries is aiming for a demonstrable version before Evolve (so less than 2 months away). Until then I'll personally continue to do most of my PCL work in VS, with the platform specific steps in MonoDevelop.