We call the cs.exe file (C# compiler), afterwards the assembly is ready if the compilation is successful. In C# projects, it is no such type of story. Althought we can't work without a linker in C/C++ projects. But they are not usually used to "link files together". The obj folder contains compiled assembly files. NO such entries for each code files! This article is talking about C# projects. There is no such thing that " We have two folders because the compilation process goes through two steps, compiling and linking.", or that " In the “obj” folder we have entry of each code file compilation." Great tip, Scott.The statements about the stuff in the obj folder are so wrong that I have not voted it at all.
Note that I didn't need the additional namespace page directive because this assembly has no namespace. aspx page header, but this modification is safe to make in the original source file and can be permanent: You also have to make a slight modification to the child. If you don't do this, you'll get "Assembly not found" exceptions. This sets up the probing path for the child assemblies. To get this to work, all I had to do was make one small change to the parent app Web.config: In my case the folder structure was like so:Īs you can see, I added a pre-compiled utility WebFileManager to the existing Linktron5000 website by dropping it into a subfolder, binaries and all. Scott documents it perfectly I'm here to tell you that I tried it, and it works. What's really cool about this is that it lets you build a pseudo plugin architecture into your existing ASP.NET website. About a week ago, Scott Hanselman posted a neat tip on deploying multiple /bin folders in an ASP.NET application.
0 kommentar(er)
