is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!) - ADO DAO RDO RDS

This is a discussion on is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!) - ADO DAO RDO RDS ; is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!)...

+ Reply to Thread
Results 1 to 4 of 4

is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!)

  1. Default is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!)

    is it possible to mark my CLR function as UNSAFE in code or visual studio
    anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me
    having to manualy deploy in tsql!)


  2. Default Re: is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!)

    What are you after?
    I mean, why would you want to mark assembly unsafe?

    --
    Miha Markic [MVP C#, INETA Country Leader for Slovenia]
    RightHand .NET consulting & development www.rthand.com
    Blog: http://cs.rthand.com/blogs/blog_with_righthand/

    "DR" <softwareengineer98037@yahoo.com> wrote in message
    news:OojmIfNIIHA.3768@TK2MSFTNGP06.phx.gbl...
    > is it possible to mark my CLR function as UNSAFE in code or visual studio
    > anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of
    > me having to manualy deploy in tsql!)
    >

  3. Default Re: is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!)

    DR,

    This is not the best newsgroup to ask this.

    I suggest news:\\microsoft.public.dotnet.languages.csharp

    Cor

  4. Default Re: is it possible to mark my CLR function as UNSAFE in code or visual studio anywhere so that wehn vs deploys, it creates unsafe assembly? (instead of me having to manualy deploy in tsql!)

    Cor is confused. I think he meant microsoft.public.sqlserver.clr.
    This is NOT a C# issue. All of my CLR Executable examples are in VB.NET.

    As to the question: When the assembly is created in Visual Studio it's
    possible to set the CREATE ASSEMBLY option as needed in the Project
    Properties. It's also do write the TSQL yourself and specify the Unsafe
    (whatever) in the CREATE.

    --
    ____________________________________
    William (Bill) Vaughn
    Author, Mentor, Consultant, Dad, Grandpa
    Microsoft MVP
    INETA Speaker
    www.betav.com
    www.betav.com/blog/billva
    Please reply only to the newsgroup so that others can benefit.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    __________________________________
    Visit www.hitchhikerguides.net to get more information on my latest book:
    Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
    and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
    -----------------------------------------------------------------------------------------------------------------------

    "Cor Ligthert[MVP]" <notmyfirstname@planet.nl> wrote in message
    news0315865-D1DB-4D1F-A1D9-64D9C8B72C92@microsoft.com...
    > DR,
    >
    > This is not the best newsgroup to ask this.
    > I suggest news:\\microsoft.public.dotnet.languages.csharp
    >
    > Cor

+ Reply to Thread
« A few different questions... | Saving a whole datatable to SQL server 2000 »