Add DLL to ASP.NET vNext Project - asp.net

My goal is to add a reference of my ASP.NET vNext to the old MySql.Data.dll. I think that this should be possible.
I put it in a NuGet package but if I compiled my project, I receive an error message.
Anything there is wrong.
Is there a guideline anywhere showing how to add DLL references? I searched a lot until now, but haven't had found anything.

I assume this is same question as the post below? If you still have questions please do let us know.
http://forums.asp.net/t/1998097.aspx?Add+NET+4+5+Assembly+As+Reference+

One workaround is to create a class library project with your library reference. Then use a project reference from your website to the class library project.

Related

Can't mport javafx

I'm using Netbeans 8.0.2. I used the wizard to created a Java class library project so I could share a class among several projects. I now want to add some capability that requires me to import from javafx (SimpleStringProperty). Fix imports didn't work and Intellisense says it doesn't know javafx.
I looked at the Project Properties | Libraries setting of one of my JavaFX applications and I see javafx.classpath.extension. I think I need this, but I don't know how to add it. I searched and someone suggested adding the jdk's jfxrt.jar file to the compile libraries, but that didn't work.
Is the lack of javafx.classpath.extension my problem? If so, how do I add it?
I finally found this bug that addresses this: Bug 213219 .
Basically, you: "...go to Project Properties, Deployment panel, and check "Keep JavaFX Runtime on Classpath"..."
Thanks everyone!

Can I create my own template to scaffold my own WebAPI controller when using WebAPI 2 and VS 2013 RC Update 2?

I tried to use the scaffolding but there are so many changes I need to make for it to meet my needs. Is there some way I can make my own template so I can scaffold my own controller automatically.
Please note I just updated to the latest release of VS2013 RC Update 2. Not sure if there is any new functionality in that which would help me.
thanks,
There are two ways that customs scaffolders are supported:
Write a new scaffolder as a VSIX extension. This will be available for any project on your machine, but does require installing the VSIX to share. A sample walkthough is provided here
Customize the scaffolding T4 templates for your project. This will be available only in the project where you do it, but should not require any further custom installation once it's there (note: setting it is simplified by having the SideWaffle extension installed). A sample walkthrough can be found here
Never done it before, but this may help http://blogs.msdn.com/b/webdev/archive/2014/04/03/creating-a-custom-scaffolder-for-visual-studio.aspx

Jar to include to use javax.annotation.*

I'm a bit confused. I need to compile a project in jDeveloper 11.1.1.6.0. The server side of the project is deployed on the Glassfish server. On the machine of the project's creator everything compiles without any problems.
Using project properties -> Libraries and Classpath I added the libraries such as gf-client.jar, security etc. from $glassfish_home/glassfish/modules and some others (e.g. hibernate3.jar from hibernate dir).
When I try to compile the project I receive the following errors:
package javax.annotation.security does not exist
and
package javax.persistence does not exist.
I suppose that I miss some jars to include. I tried to find which jars (from Glassfish or from JDK) contain javax.annotation.* and javax.persistence.* but I couldn't.
If you have any ideas I would be thankful!
I was having the same problem and was able to solve it by adding a couple of dependencies to the Maven pom.xml file. See this answer for more details.
So I found the source of the problem. The application consists of 2 projects, of which only one (mentioned in the question) uses EJB. I'm not sure if it is the way it should be, but I tried adding ejb-files to another project. And after clean all and rebuild all it compiled like a charm for me. I hope this will help somebody in the future.

Downloaded StructureMap but seems to be missing the Log4Net.Dll

I am currently following instructions in a book to develop an application. It asks me to download StructureMap and then move the StructureMap.Dll file and the Log4Net.dll into the bin files. The problem is there doesnt seem to be a Log4Net.dll file in the StructureMap files, the only other dll apart from the StructureMap.dll is the Rhino.Mock.dll. can anyone help?
Thanks
Rachel
StructureMap underwent a bit of an overhaul recently, so it's possible that a dependency on log4net was removed during that process. In any case, StructureMap does not currently require log4net. Here's a quick screenshot from Reflector showing as much:
(source: cryptofreak.org)
It might be worthwhile to find out which version of StructureMap the book is referencing and try that one rather than the latest.
I'm developing the same social networking site too. Download StructureMap V.1.1 from here, where you will find both the dlls:
http://github.com/structuremap/structuremap/downloads

Tracking down references to a service

I get this error in my ASP.NET 3.5 website:
Error 3 Cannot update project reference 'Services'. Source project not available.
How can I track down any reference to this assembly so I can then delete it? It must be called from somewhere. I no longer have an assembly in my project with this name.
Thanks
Check your references: in your Reference Paths Dialog Box (Visual Basic) or the Reference Paths Page, Project Designer (C#, J#).
See this link in MSDN for details: How to: Add or Remove References in Visual Studio
I didn't have much luck with the previous answer for web projects, so I thought I'd offer another way. Web project references are kept (non-intuitively) in the solution file, and with care you can edit this file to remove the reference.
Close the solution if you have it open, then open solution file in a text editor.
Search for name of the project that failed to load. This should bring you to the configuration section for your web project.
Inside that should be a line beginning with "ProjectReferences", with a semicolon-separated list of projects.
If you CAREFULLY remove the offending project, which includes a GUID and the assembly name for the project, then save the solution file, you should be good to go.
Be sure to allow yourself a backup strategy in case something goes wrong.
I'm using Visual Studio 2008; I don't know if it works exactly the same way in other versions.

Resources