Bug 369 - Symbolic links not properly removed in Windows packaging
Summary: Symbolic links not properly removed in Windows packaging
Alias: None
Product: Runtime
Classification: Mono
Component: packaging ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Alex Corrado [MSFT]
Depends on:
Reported: 2011-08-23 15:49 UTC by Alex Corrado [MSFT]
Modified: 2011-09-02 13:23 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Alex Corrado [MSFT] 2011-08-23 15:49:08 UTC
All symbolic links should be removed when creating Windows packages for Mono.

A problem encountered by a user:

Downloaded and installed windows version 2.10.4 of Mono the other day
onto a Virtual XP platform.

Ever thing seemed to install ok. However, when trying to run xsp, to
test that things are working, I get the following:

> Cannot open assembly
> 'C:\PROGRA~1\MONO-2~1.4\lib\mono\2.0\winhack\xsp2.exe': File does not
> contain a valid CIL image.

on investigation the file xsp2.exe pointed to is only 108 bytes! The
file is actually a symlink containing:

> !<symlink>ÿþ../gac/xsp2/2.10.2.0__0738eb9f132ed756/xsp2.exe

This should be fixed in Mono 2.10.5
Comment 1 Alex Corrado [MSFT] 2011-09-02 13:23:14 UTC
Fixed in mono 2.10.5