In a project using .Net4 - should there be problems associated with DLLs built for older versions of .Net? We are talking about a third party DLL.
I ask this as a general question. In particular, I have a problem referring to FluentNHibernate.dll - built with .Net3.5. It worked fine before I upgraded my project from .Net3.5 to .Net4.
No, in general, you can have a .Net 4.0 project referencing any DLL, even if they were compiled against older versions of .Net.
: , , / IL, , .NET.
Source: https://habr.com/ru/post/1742450/More articles:What is a good template for binding a collection of WCF objects in Silverlight? - data-bindingWhy do some asp.net controls retain their state, although its EnableViewState property is false? - asp.netNeed a sorted dictionary designed to search for values with keys that are less or greater than the search value - dictionaryBuilt-in functions in pl / sql? - functionStandardServletContainer for target runtime in Eclipse - javaJava - abstract class, equals () and two subclasses - javaJQuery $ .unique () problem, i.e. - jqueryIs it safe to delete from SortedList during iteration - c #Override to_xml to collect ActiveRecord objects - xmlHow to enter the ApplicationData user folder by registering in the corporate library? - .netAll Articles