#39 Users Frustrated With Sushi to the Point of Dumping It

[Doug Ransom]

I received this email from a suhi admin.

"I just tried installing using the latest .MSI, downloaded
off sourceforge. It didn't work because it's looking for a
SUSHI.CAB file which I didn't download because it's not
in the download area of sourceforge. SushiWiki is totally
bogus. I'm going to start seriously looking for another
wiki implementation. I think the only things we need are:
saving all versions of all pages for all time
knowing who edited what and when".

I have been trying to get sushi to compile off and on
since April 2003 (its now March 2004) so we could tweak
it and fix bugs. Never once could we do this via source
forge.

We can't install the latest, we cant compile it to fix bugs.

Until sushi gets a clean compile every build and some
way to install, all the hard work of the developers is for
naught. I think for sushi to be successful, its more
important to have an open source project that compiles
and installs than more and more features that only the
core dev team can use.

I suggest that the key focus of the sushi should be (in
order):
1) support a command line build so one command builds
the entire product.
2) Detailed instructions on how to set up a deveoper
environment to work on sushi
3) Detailed instructons on how to deploy sush without
an installer
4) A working installer.

[Yann Schwartz]

Logged In: YES
user_id=785251

There is a build file which can be used to compile a working
SushiWiki site.

It's not seamless yet (I'm working on a version needing only
the build file to checkout automatically all files from CVS).

To get a working compiled sushiwiki :

Under a root folder, checkout these modules from CVS :

Build
SushiWiki
SushiWikiLib
SushiWikiPlugins
WikiLibTest

Get Nant 0.84 (http://nant.sourceforge.net/ to get a working
version) and call "nant.exe" from the Build directory.

All files should be built then, and the SushiWiki directory
should be ready to be deployed.

When everything is streamlined (should be in a week or two)
SushiWiki MSi files should be buildable this way too.

The nant build file is a raw cut right now. If you
experience problems with it, let me know.

[Robert Brinton]

Logged In: YES
user_id=135065

I haven't tried the Nant build process, but I was able to
checkout from CVS the previous version and get it to compile
using Visual Studio.

I just got the sources (with only a couple of minor changes)
from the RC2 zip to build using studio tonight. I had to re-
create the solution and projects as I was unable to load the
ones that were included.

(Keep working on the Nant build process as I agree that
command-line implementations seem to make it easier to
repeat results.)

I am currently running the previous version on an intranet at
work. I found several small things and fixed them as I went. I
did not list them on the bug list as I kept expecting a new
release 'any day now'.

When I first found issues (about six months ago) and started
correcting them I volunteered to help with development but I
was told to check back in a couple days after the next
release.

I like the new default look (much better than the previous
one).

I like the in-place table editing without having to edit the
whole page.

I like the calendar and events concept, but I'm not sure I like
how and where the events are stored. While playing with
events, I found my first couple of bugs. I will go post them to
the bug list right away.

[Nobody/Anonymous]

Logged In: NO

Has any developer actually TRIED to compile this from
Sourceforge, clean, from scratch?

- is it SushiWiki, or SushiWikiWeb? The web share folder in
the tarball is named "SushiWikiWeb", that seems to be what
Visual Studio expects, but fresh from CVS it's SushiWiki.
Minor, but annoying.
- there are missing files. First thing I get when trying to build
(using Visual Studio.NET) is a missing file
pub\LienAutomatiqueHtml\GenLexer.cs that prevents me from
compiling it. Can't find it in the tarball (there's not even a
pub directory in the zip file) and it's not in CVS.

I would suggest that a developer download a completely
clean version from CVS -- if you can't follow chbeurtz's
instructions (which you can't, not from scratch), then this
isn't ready yet.

I can see why dransom is getting complaints, this is pretty
frustrating. I'd be less conserned with having nAnt build it,
Studio would be fine -- but one should be able to compile and
deploy this in about 4 easy steps:

1) Download from CVS (all 5 modules that chbeurtz lists in
his/her post)
2) Create the Web share in IIS
3) Open the sln file using Visual Studio.net
4) Build and run.

[Robert Brinton]

Logged In: YES
user_id=135065

I have had poor luck with just installing and opening the
associated SLN files. I think that there are just too many
variables available. (Studio Versions, path settings, installed
tools, build directory, windows setup and versions, IIS
configuration, ...)

I'm currently building using the source zip file from the RC2
release (SushiWiki-v1-rc2-src.zip).

I first re-created all of the solution and project files to match
and then set the references so they pointed to my framework
and projects. This allowed me to build the project with
studio. (There is however something wrong with the sources,
designer refuses to open the pages--not a big deal for me, I
prefer the HTML anyway.)

(Error is: The base class 'Wiki.GUI.WikiPage' cannot be
designed)

I have recently finished modifications to the Nant build to
make it build successfully with those sources.

I was going to attach it, but I can't attach it to a comment.

The only really strange thing I had to do was to exclude the
file 'WikiInstall.aspx.cs' from the SushiWikiWeb directory. It is
in that directory from the RC2 zip, but it will not compile with
the rest of the *.cs files.

[Yann Schwartz]

Logged In: YES
user_id=785251

>>Date: 2004-03-10 08:35
>>Sender: nobody
>>Logged In: NO

>>- is it SushiWiki, or SushiWikiWeb? The web share folder in
>>the tarball is named "SushiWikiWeb", that seems to be what
>>Visual Studio expects, but fresh from CVS it's SushiWiki.
>>Minor, but annoying.

The sln file in /Build should do. You first have to Create a
virtual directory named SushiWiki pointing to SushiWikiWeb
(weird, I know).

>>I would suggest that a developer download a completely
>>clean version from CVS -- if you can't follow chbeurtz's
>>instructions (which you can't, not from scratch), then this
>>isn't ready yet.

If you checkout the Modules (starting with the Build module)
it should work. I can"t test it right now (I'm in Belgium
and I can't access the CVS from where I work), though.

I will test it thoroughly saturday, update the sln file in
/Build if it's not working properly, and post on the
sushiwiki home
a step by step guide to set up sushiwiki for development.

[Yann Schwartz]

Logged In: YES
user_id=785251

I've corrected some project files and fixed some stupid
typos in the nant build file. I've tried an install from
scratch using only what's in the CVS and it worked.

I've also written a step by step guide to get sushiwiki up
and running from CVS.

See
http://egroise.europe.webmatrixhosting.net/Wiki.aspx?page=SushiWikiDevHowTo