I have a vaadin 8 application that builds and runs fine with versions up to 8.14.3. along with a vaadin pro subscription. Since 8.15 and the change in to CVDLv4 the application builds but doesn't run.
I have installed the license for vaadin charts and it is recognized, as I get: "Vaadin Charts 4 registered to ### (Pro Tools subscription)" during build. If i remove the license file compile fails as expected. I've also tried the license as a parameter with the same results.
When I run the application (on Netbeans), I get: "java.lang.RuntimeException: Unable to validate subscription". I thought subscription validation was only done during the build. In any case it should be able to validate the license as it did during the build. I've tried all the suggestions I could find (firewall, adblocker etc are off), tried different browsers etc. but couldn't get it to run.
Vaadin 8.14.3 is the last release under Apache 2 license. The subsequent releases are offered under commercial extended maintenance.
Related
I understand .NET 7 is new, but I think a workflow that should work out-of-the-box is to create a new MAUI template project (".NET MAUI App"), choose a name for that, and successfully build the just-created project. On my system, this consistently fails with this warning:
Severity Code Description Project File Line Suppression State
Warning XA1004 File 'obj\Debug\net7.0-android\lp\101\jl\res\..\res.zip' already exists. Ch0501 C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.EmbeddedResource.targets 36
While I do not like this warning on a brand-new project, there is another issue: I nothing happens when I launch the project by clicking Windows Machine:
For .NET 6, this would launch a "welcome" form, welcoming you to MAUI. Now, the program runs but then ends without presenting any UI.
How are users expected to get started with MAUI with issues like this? I will single-step and debug to try to see what's going on, but shouldn't this just work??
Does anyone familiar with .NET 7 MAUI know why I am encountering these issues? What do I need to do to run the app so that it displays the MainPage "welcome" form on Windows?
I decided that I don't have time for MAUI's broken-ness. I visited several devoted MAUI forums, and many users have complained about functionality that's broken out-of-the-box using the latest of all available IDEs, frameworks, and tooling. MAUI's bug list is ever-growing and outpaces the rate at which bugs are fixed (often needing further fixes due to lack of QA testing). The fact that my basic question about MAUI received a few dozen reads (as of this writing) and no useful reply suggests that broad understand of MAUI fundamentals does not yet exist in the developer community. I don't have time or interest in being an extension of MAUI's QA team and to work with tools whose "hello world" out-of-the-box sample cannot run on a new installation. It's just ridiculous.
I installed Uno 4 instead, and their "hello world" app ran without a hitch (using .NET 7) on Windows and on my tethered Android device. So I plan to use Uno for my multi-platform C#/.NET 7 project. Maybe in the distant future, MAUI will be ready to be reconsidered--for now, it's a pet project that desperately needs some professional attention.
I'm working on a legacy application that uses these third party controls. I'm moving the application to new infrastructure but the ComponentArt UI elements are reporting that they are unlicensed, shown in the image here 1. We have the license in the bin folder and I have tried to install the available ComponentArt nuget package to no success.
I open visual studio and do file->new project.
I select cloud->service fabric application. Then I pick Stateless ASP.NET Core. In the last window I select Web API and change the authentication to windows authentication.
When I do this and then compile the application, I get errors saying that System.Fabric, Microsoft.ServiceFabric.* are missing.
How can I get this to work?
NOTE: I have Visual Studio 2017 15.2. I downloaded and installed what I think is the most recent tools for service fabric. My "Extensions and Updates" says I have version 1.6.20170504.1.
UPDATE - This was due to the project having a dash in the name. It appears that the template cannot cope with dash casing your project name. (It had nothing to do with Windows Authentication.)
UPDATE - This was due to the project having a dash in the name. It appears that the template cannot cope with dash casing your project name.
This seems to be a problem with the template. If you don't select Windows Authentication, then it will compile fine.
In a project without windows authentication, the Nuget assemblies are:
Microsoft.ApplicationInsights.AspNetCore
Microsoft.AspNetCore
Microsoft.AspNetCore.Mvc
Microsoft.Extensions.Logging.Debug
Microsoft.ServiceFabric
Microsoft.ServiceFabric.AspNetCore.WebListener
Microsoft.ServiceFabric.Data
Microsoft.ServiceFabric.Services
When you select Windows Authentication, only the top 4 are added to the project.
If you add the four missing NuGet packages (the ones in bold above) then the project will compile just fine.
I'm developing an Eclipse plugin and i've run into this problem several times already.
I always keep my Target Platform updated for the latest (stable) Eclipse release so that i test my code against all the recent updates, fixes etc.
However, this may (and have) result in accidental breakage of backward compatibility of my plugin, e.g. when i accidentally use new API that did not exist in the Eclipse version i aim to support.
Or, more sneaky example, in 4.6 Eclipse moved to Java 8 and some interface methods got default implementations. Now when i implement these interfaces my IDE doesn't automatically generate empty implementations for those methods and no error is generated. If i install and run this code against a previous Eclipse version these methods will throw AbstractMethodError since no implementation has been provided.
So my question is: is there a tool to further restrict API my Target Platform provides to some earlier Eclipse API version?
Is API Baseline an appropriate tool for this? Because i couldn't get it to work like this. (It allowed even non-baseline method calls not to mention the more complex default-methods example.)
You can use multiple target platforms, switching between them doesn't take long. For testing Stack Overflow questions I have one Eclipse install with 10 target platforms.
So have a target platform for the oldest release you want to support as well as your current release target platform and check the code runs against that.
It is particularly important to test with the actual Target Platform if you want to support Eclipse 3 releases as the were large changes going from Eclipse 3 to 4.
I am installing ez publish(CMS) in my xampp...
however in this section of installation
SITE PACKAGE
I can't proceed even though I can click next.. I bet the site package is mandatory... I need your help guys... btw, I am installing 2013.5 version
here's the error
Error
Invalid package
Remote repository URL: http://packages.ez.no/ezpublish/5.0/5.0.0/
I've tried uploading the ezwebin_site.ezpkg in the remote repository still I can't proceed... thanks in advance.
Site Package selection step within the Setup Wizard is more or less required (you must select one package using the ratio buttons) to complete a proper eZ Publish installation first time.
Notice the 'Help' sidebar content, "The type of site will choose some basic settings for toolbars, menus, color and functionality. It is possible to change these settings at a later time.".
This is to remind new users that you first use the setup wizard for your first time installation of eZ Publish and then you can re-configure eZ Publish settings, design, extensions, etc manually as much as you desire / require. You can customize almost any part of eZ Publish, once you have it installed and setup properly.
It is recommended for new users to install the 'Website Interface' (with content) package for your first installation. Again you can change all it all after you have completed the default installation and have a working default installation.
More experienced developers may choose to use the 'Plain site' package (with no content, and significantly less default functionality and helpful tools) but this option often causes extreme confusion to new users / developers (who need the tools provided in the 'Website Interface' package to get started using eZ Publish quickly) as it omits expected content classes, default content use case examples, roles / policies, default settings use case examples, ezwebin design extension and much more. As such any package choice other than 'Website Interface' (with the version of eZ Publish you are using) is very strongly discouraged.
Advanced Developers with an already setup installation can create their own site packages to reuse in the future to simplify configuration of a default installation.
Resolution Edit: During an extensive stackoverflow and irc chat it was determined that the user asking the question lacked the WAMP server (PHP modules) support required by eZ Publish 5.x which is why the user was having installation setup problems. Specifically the user was missing the required php curl module which is used / required by the setup wizard to download site packages. The user was strongly recommended to replace Xampp (on win32) with Bitnami (for eZ) which provides for all the requirements of eZ Publish 5.x by default and has already been heavily tested and customized for use with eZ Publish 5.x. Also the user was using an older version of eZ Publish 5.x (2013.5 community build) which only supports PHP 5.3 and the user's Xampp PHP version was PHP 5.6.8 which requires at the very least eZ Publish 5.x (2014.11 community build).