Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I just came across this directory and it seems totally a different world.
Anyone knows what's that?
The .NET Framework is an environment (runtime) on top of which code executes. A .NET assembly is a container for code written to execute using the .NET Framework. Assemblies can be either libraries (.dll files) or executables (.exe files).
The .NET Framework has a set of common libraries that can be used by any application which executes under the control of the .NET Framework and the C:\Windows\Assembly folder is where these common libraries are stored.
The reason that the folder displays differently to other folders is because of the special role of this folder as the common location for shared libraries. Microsoft created a special view of this folder that provides easy access to information about the assemblies in that folder as well as providing easy access to operations commonly performed on an assembly such as the Uninstall option in the right-click menu for an assembly.
Using a search engine
It is used to store .NET assemblies,
which can be shared between
application.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I am trying to build jpeg_gpu, and the current Visual Studio error is "Cannot open 'GL/glcorearb.h' ".
I can find the file 'glcorearb.h' online at khronos.org, but I'm not entirely sure if I am supposed to just fetch this one file, or if it's supposed to be installed as part of some other library. It doesn't seem to come as part of GLFW or GLEW.
What is the most sensible way to obtain glcorearb.h? On its own, or as part of a larger library?
If it should be downloaded on its own, where is the most sensible place for it to live on a Windows machine for Visual Studio to find?
Khronos is the official group for OpenGL matters. They publish the headers.
People at GLFW, GLEW, VS, or whatever, download the headers and incorporate in their code. Sometimes they do some small changes, mainly for 32/64 bit types or compiler adjustments.
If you compare glext.h and glcorearb.h you will see that the later doesn't include any stuff for OGL before 3.2, while the glext.h contains all. So, general libs (like GLEW) will provide and use glext.h instead of glcorearb.h.
If your code requires glcorearb.h then just fetch it from Khronos and put it in the same folder where glext.h is.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I am learning Win32 API. I recently stumbled upon the topic of dll.
I have understood it well, but now I want to find more about dll files.
for example, one of my project uses 38 different dll files, I have made a list of all these dll files.
I know many of these files are from the softwares that i have installed,
but there are many windows specific files as well.
Where can i find information about these dll files given by windows.
All I want to know is what these files do?
I'd appreciate if someone would point me in the right direction, perhaps a good windows book.
The only way to have clues on why dll is linked is to use Depends.exe. It's in the tool section of visual studio
The most up to date version is there http://www.dependencywalker.com/
It will tell you for each dll what function in each dll is linked and if the dll is linked to your product or included indirectly.
It wont help on that specific problem, but there are more useful tools which unfortunately are not packaged with visual studio highly specialised but useful when needed http://technet.microsoft.com/en-us/sysinternals/bb842062
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to make a quite simple application in multiple devices using xamarin (iOS and Android).
So I read/think that the best way to doing this is to put one folder (shared between all projects) that contains all the:
DataLayer (for physical storage)
DataAccessLayer (support data operations)
ServiceAccesslayout (communicate with an external API)
BusinessLayer (Application Facade)
And for the view, the applications will use their custom language
So first question, does it sound great?
Second: How add that kind of folder, that should be updated in every project in Visual Studio 2012? Actually I have one solution with two projects and the two projects (iOS and Android) should have that same folter (tat contains all the "core" layers)
By the way if you have already read a tutorial that talk over that question, please give it to me.
I would have a look at MVVMCross, it is a great way of sharing the maximum amount of code across platforms.
https://github.com/slodge/MvvmCross
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
On Windows 7, VB.NET Express, I have developed a simple Forms application. I don't really make use of any external plugins or anything - it just has a couple buttons, pictureboxes, GDI operations to modify some images...
And now it is complete. And I would like to already upload it. But, since this is actually the first time I try to submit something, what other details should I keep in mind when distributing my application? I mean stuff like... will my application work as expected in other machines? Other Windows versions? I am not in a proper position to test it in other machines, I fear, so I am relying the "default" settings and hoping it will simply work.
Unless you use platform-specific APIs (which are rare in your typical, garden-variety .NET application) then it should work on all versions of Windows that support your version of the .NET Framework. If the end user doesn't have that version of the .NET Framework installed, then he or she will need to get it manually. You can make that a little easier by using the built-in ClickOnce installer (Build > Publish <project name>) if you're not already using it.
Apart from that, no, there shouldn't be any problems, given that you say your application is a simple one. (And console applications can even work on Linux and Mac using Mono!)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
In my external usb harddisk when I click on only the folder names "MISC" I get the error
Microsoft Visual C++ Runtime Library
Program: C:\Windows\Explorer.EXE
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
Other folders open perfectly without the error.I tried changing the folder name but it did not help.I can use windows explorer to open/expand the folder and sub folder on the left.If I open the root of the folder MISC I get the error.Tried sfc /scannow,avg virus scan of the drive,spybot s&d scan of the system.All clean.No new program was Installed recently.Please guide what to do!
This application has requested the Runtime to terminate it in an unusual way.
This occurs when some code linked to the MS C runtime calls the C abort function. Since Explorer doesn't rely on the MS C runtime the most logical conclusion is that you have a misbehaving shell extension. Shell extensions are loaded into the Explorer process and can quite easily wreak havoc like this. I would try this disk on a different machine to test out that theory. Or find a tool that disables shell extensions.