Missing Files for Software Engineering Methodology | COMP 410, Study notes of Software Engineering

Material Type: Notes; Professor: Wong; Class: SOFTWARE ENGINEERING METHODOLOGY; Subject: Computer Science; University: Rice University; Term: Spring 2006;

Typology: Study notes

Pre 2010

Uploaded on 08/18/2009

koofers-user-do4-1
koofers-user-do4-1 🇺🇸

10 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
The following folders and files are missing from the source control but can be found in
the uploaded zip file in Final Documents library. The following list may be over
specified, that is, you may not need all the files for the solution to compile. The
underlined files may be all that is really missing.
client\extern -- folder missing, contains ICSharpCode.Share2pub.dll ( moved to
client/extern) and Irrlicht.dll
server \extern – missing files: Gentle.Common.dll (moved to server/extern) ,
Gentle.config (only the one in server/SkyNet is needed and needs to be set for “copy to
output”), ICSharpCode.SharpZipLib.dll, QuickGraph.Algorithms.dll
client\ProtoView – Irlicht.NET.dll missing. Is this the right place for this file? – Moved
to client/extern and reference in ProtoView adjusted to reflect this.
client\Controller\Resources – folder is missing, contains sky.net-logo-sm.jpg (moved to
/images)
client\Controller\skynet.ico – file missing (moved to /images)
After files are copied, you need to click on the erroneous references in the solution
explorer to refresh them so they can find the new files.
Note: On Skynet1, My Documents will be mapped back to Ownet, so don’t use the VS
default project directory. Make a directory for yourself and have VS put the local files
there when downloading from TFS.
The SQL Server instance must be the “default” ( = unnamed) instance. The SQL
Express instance installed by VS.NET 2005 is a named instance (“SQL2005”) so another
install is needed. Use the install from the SQL Express web page at Microsoft which
will, eventually in the install process, allow you to do a default instance installation.
SQL Server defaults to the default instance installation so there is no problem there.
To run the view or the dummy network, set the “startup project” to be client/controller.
To start the server only, set the startup project to be ServerMain. See the rest of the
documentation for the input parameters and operation of the view and server.
When the Sky.NET server is run for the first time, the Windows Firewall should ask if
“vshost.exe” should be allowed through the firewall. The file to allow is actually called
“server\ServerMain\bin\Debug\ServerMAin.vshost.exe”, in case you have to set it
manually.
Irrlicht may not run properly if the hardware acceleration of the graphics card is not set to
“full acceleration”. You may get strange error messages such as “Cannot load built-in
font”. A way to check if the problem is in the Irrlicht Engine is to download and run the
pre-built demos from the Irrlicht site. If the problem is in the hardware acceleration
setting, the demos will run in OpenGL or software rendering modes, but not in DirectX
modes.
pf2

Partial preview of the text

Download Missing Files for Software Engineering Methodology | COMP 410 and more Study notes Software Engineering in PDF only on Docsity!

The following folders and files are missing from the source control but can be found in the uploaded zip file in Final Documents library. The following list may be over specified, that is, you may not need all the files for the solution to compile. The underlined files may be all that is really missing. client\extern -- folder missing, contains ICSharpCode.Share2pub.dll ( moved to client/extern) and Irrlicht.dll server \extern – missing files: Gentle.Common.dll (moved to server/extern) , Gentle.config (only the one in server/SkyNet is needed and needs to be set for “copy to output”) , ICSharpCode.SharpZipLib.dll, QuickGraph.Algorithms.dll client\ProtoView – Irlicht.NET.dll missing. Is this the right place for this file? – Moved to client/extern and reference in ProtoView adjusted to reflect this. client\Controller\Resources – folder is missing, contains sky.net-logo-sm.jpg (moved to /images) client\Controller\skynet.ico – file missing (moved to /images) After files are copied, you need to click on the erroneous references in the solution explorer to refresh them so they can find the new files. Note: On Skynet1, My Documents will be mapped back to Ownet, so don’t use the VS default project directory. Make a directory for yourself and have VS put the local files there when downloading from TFS. The SQL Server instance must be the “default” ( = unnamed) instance. The SQL Express instance installed by VS.NET 2005 is a named instance (“SQL2005”) so another install is needed. Use the install from the SQL Express web page at Microsoft which will, eventually in the install process, allow you to do a default instance installation. SQL Server defaults to the default instance installation so there is no problem there. To run the view or the dummy network, set the “startup project” to be client/controller. To start the server only, set the startup project to be ServerMain. See the rest of the documentation for the input parameters and operation of the view and server. When the Sky.NET server is run for the first time, the Windows Firewall should ask if “vshost.exe” should be allowed through the firewall. The file to allow is actually called “server\ServerMain\bin\Debug\ServerMAin.vshost.exe”, in case you have to set it manually. Irrlicht may not run properly if the hardware acceleration of the graphics card is not set to “full acceleration”. You may get strange error messages such as “Cannot load built-in font”. A way to check if the problem is in the Irrlicht Engine is to download and run the pre-built demos from the Irrlicht site. If the problem is in the hardware acceleration setting, the demos will run in OpenGL or software rendering modes, but not in DirectX modes.

As of 7/31/06, the code in the source control should compile and run with no problems (other than known bugs with regards to non-operational features).