https://sourceforge.net/p/witicket/news/2007-06-22T20:00:49ZRecent posts to news2007-06-22T20:00:49Z2007-06-22T20:00:49ZTTThttps://sourceforge.net/u/iteacup/https://sourceforge.net2ed305240825349e2d564ffcbfc7bb78ad91ee52

<div class="markdown_content"><p>The new wiTicket Beta version has been released. Fully functional! No more bugs! WITH AUTO-LOOKUP! Come and see!</p></div>

2007-04-03T16:45:06Z2007-04-03T16:45:06ZTTThttps://sourceforge.net/u/iteacup/https://sourceforge.neta08370ac8c49765f31ee2059dc5b880d5b52f048

<div class="markdown_content"><p>Here it is! The Alpha 0.0.1 release!<br /> This is a WORKING prototype. Please feel free to download it, play with it, improve it, and share your improvements with others!</p> <p>This project is in its earliest stages. There is a 90% functional ALPHA prototype of the application, but lots of work yet to do. Please consider joining the team to help develop this utility and its supporting documents.</p> <h1 id="this-release-is-the-source-code-only">THIS RELEASE IS THE SOURCE CODE ONLY.</h1> <p>To use this code, you will need to<br /> 1) Copy the files to a work area on your server<br /> 2) Compile the source code to a .dll<br /> 3) Copy the .dll to the bin folder of the IIS server<br /> 4) Grant permissions for the .dll in the IIS configurations<br /> 5) Implement the web part into your Sharepoint environment<br /> 6) Setup the configuration parameters per your HelpDesk system<br /> 7) Test the solution<br /> 8) Celebrate your success</p> <p>There is currently no documentation to help you through this process, but PLEASE send us an email with your requests (or post on the forum) so that we can help you through the process. (esp. if you are a developer interested in helping get this project off the ground)</p> <h1 id="what-we-still-need">WHAT WE STILL NEED</h1> <p>1) Entry of source into 'Code' section of SourceForge project<br /> 2) Posted installation instructions (including how to grant .dll permissions)<br /> 3) Compiled DLL in download section WITH installation instructions.<br /> 4) Work out existing small bug<br /> 5) Implement several key additional features<br /> 6) Release BETA version once items 1-5 are complete.</p></div>