I replied on an old(er) post with the same issue, but am creating a separate post in hopes someone can point me in the right direction.
I'm using Visual Studio 2022 with Infragistics 22.2. I found is_res and enabled it, but am experiencing this same issue still. I tried running the Version Utility, but get some kind of error with that. I'm working with a big bowl of spaghetti code that has been handed down several times. Now it sits with my group, none of whom are actually developers. yay. If it matters, the header on the error I see is Error creating control - ig:WebDataGrid
The person who was managing the site is still with the company but has moved to a different group and management has become the responsibility of my team. He's got Visual Studio 2019 and doesn't see the error(s) I do. He insists it's due to the way VS2022 handles things versus VS2019. At this point, I'm not sure what else to do other than downgrading Visual Studio.
If you have added the ig_res folder manually, please go in design mode, right click on the designer and select “Refresh”. This would load the designer again and you will be able to see the controls on the page, with Infragistics controls having no style applied in the designer, you would still be able to interact with them and use their smart tag, however the stylistic changes would be applied once the application is running.
As for the suggestion provided by your colleague, it is correct, the issue is caused due to the differences between the designer support in VS 2019 and VS 2022. Our development team is currently working on providing this compatibility, but I am not able to give you any ETA at the moment.
If you are still not able to interact with the controls even if the designer is refreshed, what I can suggest you is reverting back to VS 2019 in order to have full designer support.
Please let me know if you need any further assistance.
Regards, Ivan Kitanov
The odd time that I didn't get the error - usually after loading another page with a similar grid, it still didn't fully display. I ended up reverting to VS2019 and it displays properly. I wish I could have figured it out under VS2022. Thanks for your help.
I'm glad I was able to help.
Thank you for choosing Infragistics!