[IronPython] IronPython Tools for existing project

Mon Jul 5 22:22:51 CEST 2010

On 05/07/2010 21:20, Dino Viehland wrote:
> We should definitely be adding relative paths so this is just a bug and I'll
> take a look at fixing it.
>
>    

Cool - any ideas on the Chiron issue? (Why it isn't building our xap 
file and if it is possible for me to tell it about the external 
assemblies it needs to serve.)

All the best,

Michael

>> -----Original Message-----
>> From: users-bounces at lists.ironpython.com [mailto:users-
>> bounces at lists.ironpython.com] On Behalf Of Michael Foord
>> Sent: Monday, July 05, 2010 8:12 AM
>> To: Discussion of IronPython
>> Cc: Sven Passig
>> Subject: Re: [IronPython] IronPython Tools for existing project
>>
>> Hello all,
>>
>> A further problem I forgot to mention is that when I add / create items
>> through the ui it puts absolute paths in the project file rather than
>> relative ones. This makes it problematic to keep the project files
>> under
>> version control where different users will have different paths.
>>
>> When I edit these paths to make them relative to the solution file /
>> project file everything seems to work - so I can create a tool to "fix"
>> the project files I guess.
>>
>> All the best,
>>
>> Michael Foord
>>
>>
>> On 05/07/2010 15:38, Michael Foord wrote:
>>      
>>> Hello all,
>>>
>>> I'm working with a team on an IronPython Silverlight application.
>>>        
>> Some
>>      
>>> of the team develop with Windows and would like to use IronPython
>>> Tools for Visual Studio, especially for its debugging capabilities.
>>> This means I need to create a Visual Studio Solution and project(s)
>>> from the existing file layout.
>>>
>>> We would like to have the project checked in under version control
>>>        
>> and
>>      
>>> I'm aware that we'll probably need to manually manipulate the project
>>> files when we add files outside of visual studio.
>>>
>>> I can create the Visual Studio solution and project file and then
>>> manually manipulate the xml to add all the folders and individual
>>> files. So far so good. (Although perhaps not ideal having to add
>>>        
>> files
>>      
>>> individually - unfortunately I was away during the discussion about
>>> whether projects should be able to operate from the filesystem or
>>>        
>> have
>>      
>>> to explicitly include files.)
>>>
>>> Next I want to be able to launch our silverlight app from within
>>> visual studio in order to be able to debug.
>>>
>>> The html file is in a folder call "devcode". This has a subdirectory
>>> called "python", which becomes "python.xap" when served from chiron.
>>>
>>> I set the startup file for the project to "devcode\index.html" and
>>>        
>> the
>>      
>>> start directory to "devcode".
>>>
>>> When I launch the app with debugging from Visual Studio I get the
>>> message that Chiron has started on port 1322 and IE opens to the page
>>> http://localhost:1322/index.html
>>>
>>> Our html page opens (so far so good again), but unfortunately fails
>>> with the following error:
>>>
>>> Line: 31
>>> Error: Unhandled Error in Silverlight 2 Application
>>> Code: 2104
>>> Category: InitializeError
>>> Message: Could not download the Silverlight application. Check web
>>> server settings
>>>
>>> So it looks like Chiron is not building python.xap. How can I fix
>>>        
>> this?
>>      
>>> The next problem is that the xaml designer doesn't work. It fails due
>>> to all the external assembly references used in our xaml. Now this
>>> itself isn't so much a problem as I know the xaml designer is ropey
>>>        
>> at
>>      
>>> the moment anyway - however Chiron is going to have the same problem.
>>> It needs to know which assemblies our app uses so that it can serve
>>> them (they are served externally rather than being included in the
>>>        
>> xap
>>      
>>> file and need an entry in the Chiron manifest.)
>>>
>>> If this is never going to work with VS tools I can move the
>>>        
>> assemblies
>>      
>>> into the xap file as we will *probably* need this later anyway in
>>> order to allow our application to be installed and run out of
>>>        
>> browser.
>>      
>>> However I had assumed I could "add a reference" to the assemblies we
>>> were using. The "add reference" dialog doesn't actually allow me to
>>> add any references... The only active button on it is "Cancel". Is it
>>> possible to add references to Silverlight assemblies used by our
>>> project? (And preferably have them picked up by both the xaml
>>>        
>> designer
>>      
>>> and by chiron.)
>>>
>>> All the best,
>>>
>>> Michael
>>>
>>>        
>>
>> --
>> http://www.ironpythoninaction.com/
>> http://www.voidspace.org.uk/blog
>>
>> READ CAREFULLY. By accepting and reading this email you agree, on
>> behalf of your employer, to release me from all obligations and waivers
>> arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-
>> service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-
>> disclosure, non-compete and acceptable use policies ("BOGUS
>> AGREEMENTS") that I have entered into with your employer, its partners,
>> licensors, agents and assigns, in perpetuity, without prejudice to my
>> ongoing rights and privileges. You further represent that you have the
>> authority to release me from any BOGUS AGREEMENTS on behalf of your
>> employer.
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>>      
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>    

-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.