Okay, thanks, it's not a big deal for me that I'm self-signing since I'm not 
distributing, but I just wanted to make sure I was doing the right thing..
 
Thanks,


  _____  

From: Curt Hagenlocher [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 28, 2008 2:21 PM
To: [EMAIL PROTECTED]
Cc: Dave Fugate; Discussion of IronPython
Subject: Re: [IronPython] Building from source


If you need a strongly-named assembly and can't wait for the next beta, then 
yes, that's your only choice.  The next beta is expected around the second week 
of September, if I remember correctly.


On Thu, Aug 28, 2008 at 11:15 AM, hellosticky <[EMAIL PROTECTED]> wrote:


Hi, any ideas here? Should I just rebuild from source and sign with my own 
strong key?
 
Thanks,


  _____  

From: hellosticky [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 27, 2008 2:35 PM
To: 'Dave Fugate'; 'Discussion of IronPython'; 'Curt Hagenlocher'
Subject: RE: [IronPython] Building from source


Thanks Dave, I have SP1 and I'll figure out how to build 2.x binaries with 3.5. 
Do you have any idea about:
 
error CS1577: Assembly generation failed -- Referenced assembly 
'Microsoft.Scripting' does not have a strong name
 
Thanks,


  _____  

From: Dave Fugate [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 27, 2008 2:33 PM
To: [EMAIL PROTECTED]; 'Discussion of IronPython'; 'Curt Hagenlocher'
Subject: RE: [IronPython] Building from source



Yes, .NET 3.5's msbuild can be used to generate IronPython (2.x) binaries that 
will run under .NET 2.0 SP1 in the manner I showed below.  This is what we use 
for generating IronPython Alpha/Beta/etc releases.  Please note that you won't 
be able to run IronPython 2.x without SP1 of .NET 2.0 (or alternatively .NET 
3.5) installed though.

 

It hasn't been possible to build IronPython.sln under Visual Studio 2005 for a 
couple of release cycles.

 

From: hellosticky [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 27, 2008 9:34 AM
To: Dave Fugate; 'Discussion of IronPython'; 'Curt Hagenlocher'
Subject: RE: [IronPython] Building from source

 

Hi Dave, I was using a build from last night's source by Michael Foord. They 
didn't have a PublicKeyToken and in VS 2005 I got the error:

 

error CS1577: Assembly generation failed -- Referenced assembly 
'Microsoft.Scripting' does not have a strong name

Can I use your MSBuild (using 3.5) to target 2.0?

 

Thanks,

 

  _____  

From: Dave Fugate [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 27, 2008 12:25 PM
To: [EMAIL PROTECTED]; Discussion of IronPython; 'Curt Hagenlocher'
Subject: RE: [IronPython] Building from source

Hi, the source updates to CodePlex's TFS repository and the source zip files 
should not even include the ability to delay-sign  assemblies.  I've just 
verified this is still the case with the update to CodePlex yesterday.  Which 
IronPython binaries are you trying to run and what error message are you 
getting?

 

The other thing is you shouldn't need Visual Studio 2008 to build the latest 
IronPython sources from CodePlex's TFS repository.  You just need .NET 3.5 
installed and the following should work:

                pushd %WHEREEVER%\IronPython-38029\IronPython_Main\Src

                C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild IronPython.sln

 

Dave

 

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of hellosticky
Sent: Wednesday, August 27, 2008 7:51 AM
To: 'Curt Hagenlocher'; 'Discussion of IronPython'
Subject: Re: [IronPython] Building from source

 

I can't even run DLR/IronPython without a strong name, so that'd be nice :). I 
actually don't really mind signing them myself for now

 

  _____  

From: Curt Hagenlocher [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 27, 2008 10:04 AM
To: [EMAIL PROTECTED]; Discussion of IronPython
Subject: Re: [IronPython] Building from source

You need a certificate to sign the assembly if you want a strong name -- and of 
course any certificate that Michael has or generates won't have the same key 
signature as the certificate we use to sign here.

 

For IronRuby, we've modified the export script so that building from source 
will no longer delay-sign the assembly but just leave it unsigned.  Is this 
something that people would find useful for our regular source drops?  If so, I 
can try to cajole Dave into changing the script.  He probably doesn't have 
enough work to do anyway ;).

On Wed, Aug 27, 2008 at 6:53 AM, hellosticky <[EMAIL PROTECTED]> wrote:

Hi Michael, thanks. I'll be getting VS 2008 hopefully in a week or two. By the 
way, would you be able to build yours with a strong name?
Thanks,

> -----Original Message-----
> From: Michael Foord [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2008 5:48 AM
> To: [EMAIL PROTECTED]; Discussion of IronPython
> Subject: Re: [IronPython] Building from source
>
> hellosticky wrote:
> > Hi, I downloaded the latest change set of IronPython from
> CodePlex source code tab, but the SLN file doesn't load in VS
> 2005, and running NMAKE it looks like there are C# 3.0 or 3.5
> features being used.
> >
> > How do I build a .NET 2.0 version of IronPython from source?
> >
>
> VS 2008 can build a .NET 2.0 version (and VS Express should work I
> think), but I'm pretty sure that VS 2005 won't be able to build it.
>
> I built from the latest sources last night, it is up at:
>
> http://www.voidspace.org.uk/Ipy-38029.zip
>
> (Release binaries only, 2.8mb, no warranties etc!)
>
> Michael
>
> > Thanks,
> >
> > _______________________________________________
> > Users mailing list
> > [email protected]
> > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
> >
>
>
> --
> http://www.ironpythoninaction.com/
> http://www.voidspace.org.uk/
> http://www.trypython.org/
> http://www.ironpython.info/
> http://www.resolverhacks.net/
> http://www.theotherdelia.co.uk/
>
>

_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

 


_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Reply via email to