Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 270 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Debugging in NAV 2013 throws CAS policy error
ArjanL
Member Posts: 23
Hello,
While trying to debug in NAV 2013 build 34194, I get the following error at the moment that the debugger passes the first breakpoint.
Searching the web learns me that one or more files should be unblocked. The error should be caused by files coming from a possible unsafe source (the zip with 34194 hotfix maybe?)
Does anyone know which files are involved with the debugger, or which file(s) have to be unblocked to solve this error? Or perhaps what an other solution is to this problem?
I get the error on all machines where I try to use the debugger.
While trying to debug in NAV 2013 build 34194, I get the following error at the moment that the debugger passes the first breakpoint.
An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
Searching the web learns me that one or more files should be unblocked. The error should be caused by files coming from a possible unsafe source (the zip with 34194 hotfix maybe?)
Does anyone know which files are involved with the debugger, or which file(s) have to be unblocked to solve this error? Or perhaps what an other solution is to this problem?
I get the error on all machines where I try to use the debugger.
0
Answers
Only problem I now have is that I can choose to unblock them, but that it doesn't work. When I reopen the file properties, I have the Unblock button again.