![]() I thought I would share this in case it helps someone else in the future. I also made sure that the DAL.CustSpec project was not being built by unchecking it in the Build Configuration. What I had to do to fix this error was to change the reference in the AnotherProj project from DAL.CustSpec to just DAL, deleted all the files in the Temporary ASP.NET Files folder, and then reran the website. Of course, when I ran the part that called Method1, I received a "Method not found" error. However, when I ran the website, the Temporary ASP.NET folder for the website had the DAL.CustSpec assembly in its files and not the DAL assembly, for some reason. ![]() After everything was built, my web application project had the AnotherProj and DAL assemblies in its Bin folder. User-2074037068 posted Getting error in in asp.net 47 minutes ago In my application, i under the AppCode, i have folder with name as DataLayer. The Build configuration had both the DAL and DAL.CustSpec projects configured to be built. The AnotherProj project had a reference to the DAL.CustSpec project, and not the DAL project. My main project had a reference to the DAL project and also a reference to another project named AnotherProj. The DAL project had a method named Method1, but DAL.CustSpec did not. I had two projects in my web application solution, named, for sake of example, DAL and DAL.CustSpec. I had a similar scenario where I was getting this same exception being thrown. When you create these folders and store particular types of files in them, ASP.NET handles the files in special ways. ![]() And instead of showing a message that it could not load the 4.2.0.0 version of, it returns this exception. If your Web site application includes code that you want to share between pages, you can keep the code in one of two special folders underneath the root of your Web application, the Bin folder and the AppCode folder. I had used a binding redirect like this in all other my projects, because there were exceptions as soon as it tried to load the 4.2.0.0 which I didn't have: Įxcept in this one project, where it seems it tries to load only while calling a local function that uses a as it's parameter or return type (parameter during debugging, return type when I run the tests without the debugger, also a bit strange). This seem to be known issues that should be better in 4.7.2 (see note 2). Net Standard2 to my 4.7.1-targeting project, which caused a version conflict for (4.7.1: version 4.0.0.0, the NuGet package using. However, I had just added a NuGet package that uses. In my case, the MissingMethodException was for a method that was in the same file! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |