Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV 2013 'Control Add-in Error' message when opening a page
MuadD1b
Member Posts: 2
Hi all,
I'm getting the enormously vague error 'Control Add-in Error' that contains an add-in that I've just created.
Normally I'd check the public key and DLL's in the add-in folder. But obviously I've already done that. The info is correct and the files are there.
When I attach my Visual Studio debugger to the RTC client process and run the page, I see that the control is being initialized.
The CreateControl and OnInitialize methods are being invoked and don't throw any exceptions. Therefore I conclude it's not an error in my .NET code.
Any ideas? The Windows application event log does not contain any clues.
Regards,
Erik
I'm getting the enormously vague error 'Control Add-in Error' that contains an add-in that I've just created.
Normally I'd check the public key and DLL's in the add-in folder. But obviously I've already done that. The info is correct and the files are there.
When I attach my Visual Studio debugger to the RTC client process and run the page, I see that the control is being initialized.
The CreateControl and OnInitialize methods are being invoked and don't throw any exceptions. Therefore I conclude it's not an error in my .NET code.
Any ideas? The Windows application event log does not contain any clues.
Regards,
Erik
0