Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Gjøran Jakobsen 2 posts 22 karma points
    Nov 29, 2011 @ 09:50
    Gjøran Jakobsen
    0

    Adding umbraco.dll reference in VS2008

    Hello,

    I'm having a weird problem here, working with Umbraco v4.7.1. I've been following the umbraco.tv video tutorial on creating data programmatically, and it says to reference cms.dll, businesslogic.dll and umbraco.dll in my Visual Studio project. The former two are no problem, but the latter one just shows up with a warning sign (exclamation mark in a yellow triangle, see image below), and the Properties panel shows no path, no runtime version and a version number of 0.0.0.0.

    In my project, I reference the assembly with "using umbraco.presentation.nodeFactory", and as expected this generates a compile error: "The type or namespace 'presentation' does not exist in the namespace 'umbraco' (are you missing an assembly reference)".

    I tried to copy umbraco.dll from other installations (both 4.7 and 4.7.1) to test if the file itself was broken in some way, but this didn't change anything. Am I missing something obvious? I'm kind of in a hurry to complete this project, so any help will be highly appreciated.

     

  • Bo Damgaard Mortensen 719 posts 1207 karma points
    Nov 29, 2011 @ 22:15
    Bo Damgaard Mortensen
    0

    Gjøran,

    That's indeed a weird problem. Have you, out of curiousity, tried to create a brand new project and add the reference again? And have you double-checked the .NET version of the project you've created?

    Just a shot in the dark, really :)

    - Bo

  • Gjøran Jakobsen 2 posts 22 karma points
    Jan 12, 2012 @ 10:28
    Gjøran Jakobsen
    0

    When I posted the question, I didn't really have the time to experiment a lot - much less wait for an answer here. So the way I got past my problem was actually to switch to VS2010 - then the dll reference worked like a charm.

    Anyway, thanks for the answer, Bo - you may very well have been on to something when you mentioned the .NET version of the project. I haven't really checked, but that seems a plausible explanation.

  • awm 187 posts 376 karma points
    Jan 12, 2012 @ 10:43
    awm
    0

    Yep, it's definitely the .NET version. I spent ages banging my head against a wall trying to sort out this problem a few months ago. It turned out I was basically trying to use a .NET 4.0 library in a .NET 3.5 environment.. switching to 2010 fixed it all :-)

Please Sign in or register to post replies

Write your reply to:

Draft