we are struggling with the Bug "XtraReports v18.1.3: problems with new FilterString Editor". I saw that the problem was solved with the Devexpress Version 18.1.13. We are currently using Devexpress winform-controls version 18.1.3 together with the Ideablade DevForce ORM 3.8.13. Therefore we are not able to upgrade to a version beyond 18.1.3.
You can use the AssemblyBindingRedirector which ships with DevForce to set up binding redirects to allow DevForce to work with the maintenance releases of DevExpress.
Related
I google a lot but not find any solution. Below is my problem :
I make a simple project where I use reference "IdentityServer4.Postgresql": "1.0.0"
where "using IdentityServer4.Services.InMemory" works perfectly.
But when I use "IdentityServer4.Postgresql": "2.0.0" then IdentityServer4.Services.InMemory always shows error.
That means version 2 of IdentityServer4.Postgresql not support IdentityServer4.Services.InMemory.
How can I use IdentityServer4.Services.InMemory for "IdentityServer4.Postgresql": "2.0.0"?
Thanks in advance.
IdentityServer4.Postgresql is not a part of the IdentityServer project, but sounds like a community contribution. You may have a better result by contacting the library creator.
Otherwise, you could try the official IdentityServer4.EntityFramework package that is maintained by the IdentityServer team in combination with an Entity Framework Core database provider for PostgreSQL.
The official quickstarts only show adding Entity Framework in the 8th quickstart. You'll have to do each one in succession up to the eighth one to fully understand / make sure to have the code you need.
After you have Entity Framework added to the configuration, you can support a Postgres database by just adding dependencies.
I figure this should be very simple to fix but this is driving me totally crazy because I can't find any information about this problem.
I have created a "Blank APP (Portable)" in VS2015.
Next I used NuGet package manager to update and or install:
Xamarin.Forms v2.3.1.114
Prism.Core & Prism.Forms & Prism.Unity.Forms v6.2.0
Unity v4.0.1
--
So I want to create a bootstrapper that derives from the "UnityBootstrapper" however it can't seem to find it and suggesting to me to generate a new class.
Here are the references:
In which Assembly can I find this UnityBootstrapper?
In all the tutorials there seems to be no problem inheriting from the unitybootstrapper.
There is no more bootstrapper. As noted in the release notes, this has been removed.
https://github.com/PrismLibrary/Prism/wiki/Release-Notes-6.2.0
You should be using PrismApplication now. Also look at the getting started in the docs
https://github.com/PrismLibrary/Prism/blob/master/Documentation/Xamarin.Forms/1-GettingStarted.md
I am currently developing a custom JavaFX 8 control and was about to make the first release available when Oracle released JDK u20. After upgrading to this version my control now triggers a long list of CSS warnings that look like this:
"Could not resolve '-fx-base' while resolving lookups for
'-fx-background-color' from rule '*.test' in stylesheet
test.css".
Note: I am not calling any of these suspicious methods: applyCSS(), layout(), or impl_processCSS().
What could be the possible reason for this?
The messages were caused by changes made by Oracle to the CSS engine. Custom controls that implemented the method Control.getUserAgentStylesheet() were likely to trigger them. There were a couple of work-arounds that were suggested to fix this but in the meantime release 8u40 moved the method to Region and it is now fully supported again. However, if your project also uses ControlsFX then you will still see them until you upgrade to ControlsFX 8.40.9.
I need to upgrade an existing rather large application from Symfony 2.0.15 to Symfony 2.4.x (replace with current version).
I'm not quite sure what would be the best strategy to do so. Migration critical features like forms or esi are used, of course :)
Upgrade "step by step" from one major version to another (2.1, 2.2, 2.3, 2.4)
Upgrade directly from 2.0.x to 2.4
Do you have any tips / experience to share ? Would appreciate it :)
Thanks,
Stephan
Each new version comes with an update UPGRADE-2.x.md file containing all intructions to convert your application from the immediately previous version.
I had to do that on my project as well, and I found the step-by-step method more natural and easier to manage. Fact is, there is no file such file as UPGRADE-2.0-to-2.4.md that would help you out for a direct conversion to 2.4.
I shall first recommend to make sure that none of your code uses obsolete functionnalities of Symfony 2.0 (not sure if there are deprecated parts in this version, though), because these can be removed in ulterior versions and will not be included in the UPGRADE file.
If you have done indeep modifications of the core Symfony code, you may find that some undocumented modifications are needed. For instance, there is a custom error handler in my project, extending the Symfony error handler. Well, although it was not documented in the UPGRADE file, the signature of ErrorHandler::handle() was modified and needed to be updated in my custom handler.
Similarly, I had to modify some namespaces because files had been moved in the framework code.
The conversion is still ongoing and I'm currently experiencing a weird error I'm trying to get rid of: The 'request' scope on services registered on custom events generates errors in the logs.
All my questions in this topic related to asp.net 2.0
While working on some old project when i first opened it Visual studio asked me if i want to convert project from asp.net 2.0 to asp.net 3.5. Is it safe to chose yes ?
If i chosen no in the previous question, how can i later still convert it to asp.net 3.5 ? (Visual studio gave this option in the first place, so i guess it is possible to do later)
And the last question. Is is possible to bind GridView to the List object ?
Thanks a lot for the answers.
It's safe to switch to a 3.5 site as long as you are going to deploy to a server that has 3.5.
2.0 sites can always be changed to 3.5 sites. You can remove the .suo file and reopen the solution, and I believe you will be reasked the question. Otherwise, right-click on the project in the solution explorer and pull up its properties page, then where it says target framework just change it to "Framework 3.5".
As for a Gridivew, you can bind to a List.
Soming like:
List<Customers> customers = new List<Customers>();
Populate(customers);
GridView1.DataSource = customers;
GridView1.DataBind();
Yes - but there may be minor changes required (usually outside the .NET framework. ex: crystal reports, etc.)
Yes - Project Properties >> Application >> Target Framework.
What? From Gridview to List? Either way - Yes - New List(GridView1.Items) -or- GridView1.DataSource = List;
If you have any third party components (active reports, infragistics, telerik) you need to be assured that changing .NET versions will not break or affect their behavior. That is the biggest thing I would watch out for.