Hello,

According to our Supported Environments page, Visual Studio 2019 is supported for versions 19.1 and later, so that itself is not an issue. However, I am afraid that Windows 11 OS is officially supported for Ultimate UI for Windows Forms 20.2 and later, hence the specified configuration is expected to cause issues.

My suggestion is to try to run the application on an environment having Windows 10, or alternatively keep working in the current environment by only directly updating the Ultimate UI for Windows Forms dependencies to at least version 20.2, preferably higher.

If the issue persists in this case, please, provide more details about the "broken UI component", such as name of the component, steps to reproduce, sample code-snippets, screenshots and anything else you consider relevant.

For upgrading, you might consider the topics under the Upgrading Your Windows Forms Projects section in our documentation helpful.

Additionally, please keep in mind that depending on the .NET version – .NET (Core) or .NET Framework, either NuGet packages or assemblies should be used. More information about the configurations requiring NuGet packages can be found in this topic.

In case you do go down the road of updating the Ultimate UI for Windows Forms library and do not currently have access to a newer version, please, do not hesitate to contact our sales department at sales@infragistics.com regarding acquiring a licensed version.

Meanwhile, you could always test with the Trial version, which is always the latest one and is currently with number 23.1. It can be downloaded from the “Free Trials and Downloads” page on our website. It should be supported for Windows 11 and Visual Studio 2019 with no issues.

Lastly, according to our Product Lifecycle page, the currently supported versions of Ultimate UI are 23.1, 22.2, 21.2. Having this in mind, version 19.2 is no longer supported and is therefore not eligible for developer support services neither is receiving any bug fixes or new development. So, upgrading your app is highly encouraged to be able to leverage all introduced enhancements since version 19.2 up until the latest.

If you require any further assistance on the matter, please, let me know.

Best regards,
Bozhidara Pachilova
Associate Software Developer

Hi Thomas,

Thank you for posting to Infragistics Community!

Please, note that according to our Versioning Wiki the major version of the Ignite UI for Angular library has to match Angular’s major version. This is essential for the proper functioning of our components, since they generally depend on Angular’s API, and this one can have breaking changes between major versions. Therefore, my suggestion is to also upgrade any ‘igniteui-angular’ packages that your app depends on in addition to the ‘igniteui-angular-i18n’, which is merely our localization package.

Regarding the theming errors you are facing, I am currently not able to reproduce such an error with a similar include of the theme mixin. I am afraid we also have not had similar reports yet.

What I can say is that it is possible that this behavior is due to some breaking change, needing manual modifications that might have been skipped. My suggestion is to go through our Update Guide, starting from the Ignite UI for Angular version you are upgrading from up to 16.1.x, if that is what you will be using.

In any case, upgrading to equal major versions as mentioned above will be the first step towards resolving this, as it is possible that this difference is what causes the issue.

In case it persists afterwards, please, check out this sample (or any demo from our documentation), which uses the theme mixin similar to your snippet in the styles.scss and compare the discrepancies between it and your own app that may cause the errors. The sample is against Angular and Ignite UI for Angular 16. Also, feel free to fork and modify the sample to reproduce the error and send the sample back to me, so that we can investigate it further. Of course, you could also share the complete stack trace, which will provide some more insights where to look at.

Best regards,
Bozhidara Pachilova
Associate Software Developer

Hi Peru,

The naming convention is as described in my previous reply. To find the specific parameter names, please consult the theming functions API. For your convenience here are API links for the mentioned elements and features:

Column hiding drop-down list: column-actions-theme, input-group-theme, checkbox-theme

Grid colors: grid-theme and namely variables, such as:

  —igx–grid–row–odd–background,

  —igx–grid–row–even–background,

  —igx–grid–row–odd–text–color,

  —igx–grid–row–even–text–color,

  —igx–grid–header–text–color,

Regarding customizing the IgxGrid cell styles, namely more advanced styles, such as font weight, etc. this is not achieved by using CSS variables or component themes, as they only target colors. I believe you will find the Conditional Styling topic quite helpful on the matter. For example, the rowClasses input property on the IgxGrid component could be leveraged to assign custom styles for some target rows. In case this has to be applied for all rows, the condition function could simply return true.

Please, check out the previously referenced StackBlitz sample, where I have included the above mentioned suggestions as well.

If you require any further assistance on the matter, please, let me know.

Best regards,
Bozhidara Pachilova
Associate Software Developer

Hi Peru,

Thank you for posting to Infragistics Community!

Before I proceed with assisting you, could you please confirm if under “without using any theme” you are referring to not using the SASS Component Themes, which can be included by defining the corresponding function. For instance, for the Multi-column headers feature, as described in the Styling section of its topic, this would be the grid-theme. The function accepts parameters, such as $header-background, $header-text-color, etc. that target these elements’ colors.

What I can say is that this is the most straightforward approach to customizing the components’ colors. Additionally, the themes could either be defined globally to affect all components of the corresponding type, or alternatively, they can target separate groups or instances of components, depending on the CSS scope they are included in.

If you would require only a CSS solution, the other straightforward approach I can suggest is defining the CSS variables that correspond to the different parameters that can be passed to the component themes.

Each variable name is constructed in the following format:

–igx + “component-name-with-hyphens”-“parameter-name”,

 so, for the abovementioned grid-theme $header-background parameter, for instance, the CSS variable would be:

–igx-grid-header-background

For you convenience, I have modified the Styling demo from the referenced topic to achieve the same by using CSS variables. Please, check it out here.

In conclusion, please, refer to the Styling sections of each of the listed features topics in our documentation. There you will find links to the components themes’ APIs, where you will find listed all the available parameter names.

If you have further questions about a concrete element that should be styled, please, let me know. Additionally, if this is not an accurate demonstration of what you’re trying to achieve, please, elaborate further on your requirement.

Best regards,
Bozhidara Pachilova
Associate Software Developer

Hello,

Could you please clarify which samples are you trying to run and how did you download and isntall Ignite UI for Angular? If you are referring to the bundle available on the Customer Portal named “Ignite UI for Angular 2023 Vol. 1 Complete Bundle”, I have tested running these samples on my side by using the following commands:

In the "Infragistics_Angular_v23-1\igniteui-angular-examples-LOB” directory:

npm install –force

npm run start:live-editing

While loading takes some time, on my side I am able to successfully run the samples and no errors are raised. Consequently, I am wondering what are the steps you have followed, if my assumption about the repo you are trying to run is correct.

Apart from that, can I ask if you have checked out our “Getting started with Ignite UI for Angular” topic and if you have followed the steps from there?

Also my suggestion is to check out our documentation, where for each component there are live demos, which can be opened and viewed directly in the browser, as well as forked and edited in StackBlitz. This might be a more straightforward way of quickly referring to our components features.

If you require any further assistance on the matter, we will be glad to assist you.

Best regards,
Bozhidara Pachilova

Hi Rameez,

Thank you for posting to Infragistics Community!

In order to upgrade from version 13 to the latest, which is 16.0.x, my suggestion is to upgrade both Angular’s and Ignite UI for Angular’s versions sequentially by leveraging the “ng update” command. I believe you will find our Update Guide quite informative on the matter. Additionally, the CLI offers automatic migrations, which update much of the code that requires modification. Still, there are some manual changes that cannot be covered by the migrations and they are all listed in the above referenced topic. For your case, you will need to go from “From 13.1.x to 13.2.x” to “From 15.1.x to 16.0.x” in the process of upgrading. In case you are not using a certain feature among the described, no changes are to be made.

Regarding the error you are encountering, what I can say is that it appears rather related to licensing. The licensed package is named “@infragistics/igniteui-angular”, while the trial one is only “igniteui-angular”. The error indicates not being able to find our licensed registry. So, I am wondering if you had followed the steps from our Licensing topic to setup the licensed feed?

Consequently, I am not convinced this should be a Mac-related issue, however, please note that there are alternative approaches in case the npm version is up to 8, or 9 and above. They are listed here.

If you are still facing difficulties, you could also try to set it up with an Access Token.

Finally, to verify against a potential subscription issue, I would ask you to please try logging into our ProGet site and see if you are able to access the Ignite UI for Angular packages there. You would use the Infragistics account credentials.

Best regards,
Bozhidara Pachilova
Associate Software Developer

Hi Shobhana,

I can suggest reviewing the approach and sample from this other forum thread I have recently assisted you with.

There you will find an example of the requested updating and rebinding child grid data on its parent row toggle.

Why it does not currently work for you, I cannot tell because I cannot know what code does the “this.getChildData” method executes, whether or not it is async, what is the “this.apiResponse” variable, etc. Additionally, you will have to make sure you have the proper reference to a child grid to assign its data. Debugging might help here.

Again, please, refer to the sample and approach from the other thread, which I believe will address the same questions.

Best regards,
Bozhidara Pachilova