mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #169] An attempt was made to load an assembly from a network location #143
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#143
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @majkinetor on GitHub (Dec 8, 2021).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/169
Originally assigned to: @VShawn on GitHub.
Environment
0.6.0-beta(EXE Release).NET Framework 4.84.0.30319.42000Windows 10 Enterprise 64-bits 6.2.9200.0 (2009)Error Info
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.
Stack Trace
Recent Log
@VShawn commented on GitHub (Dec 8, 2021):
not a bug of new version, check this:
https://github.com/VShawn/PRemoteM/issues/159#issuecomment-969192014
maybe put PRM in a network loaction will cause this exception?
@majkinetor commented on GitHub (Dec 9, 2021):
Nah. The location is clearly not from my machine, I don't have D drive or
D:\DemoProject. Its different bug, just looks the same.@VShawn commented on GitHub (Dec 9, 2021):
D:\DemoProjectis my coding location, saving in the.pdbfiles for show up which file and which line the excepiton occur.the issue came from
An attempt was made to load an assembly from a network location, nothing todo with locationD:\DemoProject@majkinetor commented on GitHub (Dec 9, 2021):
OK then.
I don't use network location. I just unpacked both zip files locally and started exe without my previous config.
@VShawn commented on GitHub (Dec 9, 2021):
I just reproduce
An attempt was made to load an assembly from a network locationwhen I unzip PRM to my SMB location and run it.then, no idea why this exception was thrown.
anyway, since this issue was bring by keyword matcher dll load, I can build a all-in-one matcher (https://github.com/VShawn/VariableKeywordMatcher) and replace the current one.
@majkinetor commented on GitHub (Dec 9, 2021):
Tried on another machine, different error:
Environment
0.6.0-beta(EXE Release).NET Framework 4.84.0.30319.42000Windows 10 Enterprise 64-bits 6.2.9200.0 (1607)Error Info
Access to the path is denied.
Stack Trace
Recent Log
BTW, what is the difference between two .zip files in release ?
@majkinetor commented on GitHub (Dec 9, 2021):
Tried on third machine and it worked :)
@majkinetor commented on GitHub (Dec 9, 2021):
FFS, now it also works on first one...
@VShawn commented on GitHub (Dec 9, 2021):
I didn't notice there are two zip files. one of them may build by git action.
WT...F?
what about
run as administratoron your 2nd machine?in fact I didn't touch this part of code in this update
@majkinetor commented on GitHub (Dec 9, 2021):
It works as administrator.
Then it started to work without administrator after 1 run with administrator.
@VShawn commented on GitHub (Dec 10, 2021):
next time check the access permissions at startup