Database deployment issues

I must disagree, for the reasons I said. The main thing is that there is no reason why it cannot be called a class library. When an application is either WPF or Windows Forms then it helps to specify which and members often do not and that is a problem. Developers should use the appropriate terminology when there is absolutely no reason not to.

Sam, I think it is OK to call it a DLL or Exes. I see most of the developers still use term DLL or exe, even though in .NET, both are called assemblies. 

I answered the question of when to call it a DLL. I said "Unless it is a DLL that is either unmanaged code or a combination of managed and unmanaged code then it is not a regular DLL" and in your other thread I said "The term DLL implies regular DLL. Managed programs such as C# and VB .Net cannot create regular DLLs.". So in other words, if it is developed using C# or VB then do not call it a DLL. Yes, the project creates a DLL file but there are so many types of DLLs that it can be confusing to call it a DLL.

I am sorry for being picky about terminology. I am sure that some people think it does not make enough of a difference to justify my concern. It might not matter if there was not an easy solution but there is. The reason it is such an issue to me is that so many VB programmers do not realize that VB cannot create a regular DLL and they do not try to understand.

Another way of defining a regular DLL is to say that it is a DLL that DllImport must be used in order to call functions in it. DllImport "provides the information needed to call a function exported from an unmanaged DLL". Note that it says unmanaged. The DllImportAttribute Class documentation says "the Visual Basic compiler emits this attribute when you use the Declare statement" so you might be familiar with DllImport as "Declare".

Mr. Hobbs,

I call it a ".dll" because that is the extension given to it.....it is not given the extension..".cll" for a Class Library Link, although I am aware that it is a Class Library project...and according to Microsoft, it is STILL considered a Dynamic Link Library, hence they give it the extension ".DLL"...  so when is the appropriate time to call a ".dll" file a .DLL?  I'm new to programming, and would really like to know the difference...thank you

In Help with converting from a Windows App to a .dll??? I told you not to call it a DLL. What is it? Unless it is a DLL that is either unmanaged code or a combination of managed and unmanaged code then it is not a regular DLL and it will help to call it what it is so we know what you are talking about.

So what is the "little app"? What type of project did you create when you created the project using Visual Studio?