Discussions

Can somebody give me the elevator pitch on why this Kumo thing is going to be different from live search?  Why ANOTHER search engine?  I must be missing something...right?

Ok, thanks for the feedback!

Anyone using this new model in production?  Does it have a Go-Live license?  Are we even allowed to?  Is there a production release time frame?  Looks good, works good, when can I start seriously using this tech set?

I still have had no luck figuring out why this Web Setup fails to build.  I cannot find anywhere that will give me any more descriptive output other than just 1 project failed to build.

Still looking for help if anyone has anything come to mind...

Thanks,

Jason

Ok, so the important part that I'm talking about is at the end of this big blob, but this is from the output window.  Where else can I look for what is going wrong as this doesn't seem to be helping me at all:

This is from the output window:

------ Rebuild All started: Project: STDFReportPortal, Configuration: Release Any CPU ------

c:\WINDOWS\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:TRACE /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Configuration.dll /reference:"C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll" /reference:"C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll" /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:"C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.Linq.dll" /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.dll /reference:"C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Web.Extensions.dll" /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.Mobile.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Web.Services.dll /reference:c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:"C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll" /debug:pdbonly /optimize+ /out:obj\Release\STDFReportPortal.dll /target:library ContentServer.designer.cs Default.aspx.cs Default.aspx.designer.cs EFSetup.aspx.cs EFSetup.aspx.designer.cs PRONumberLookup.aspx.cs PRONumberLookup.aspx.designer.cs ProofOfEmail.aspx.cs ProofOfEmail.aspx.designer.cs Properties\AssemblyInfo.cs Properties\Settings.Designer.cs STDFReportPortal.Master.cs STDFReportPortal.Master.designer.cs UnbilledMissingDocs.aspx.cs UnbilledMissingDocs.aspx.designer.cs

Compile complete -- 0 errors, 0 warnings

STDFReportPortal -> C:\projects\StandardForwarding\STDFReportPortal\STDFReportPortal\bin\STDFReportPortal.dll

------ Starting pre-build validation for project 'STDFReportsSetup' ------
------ Pre-build validation for project 'STDFReportsSetup' completed ------
------ Rebuild All started: Project: STDFReportsSetup, Configuration: Release ------

Building file 'C:\projects\StandardForwarding\STDFReportPortal\STDFReportsSetup\Release\STDFReportsSetup.msi'...
Packaging file 'TopBannerBg.gif'...
Packaging file 'TopBannerTitle2.gif'...
Packaging file 'ProofOfEmail.aspx'...
Packaging file 'save_ico.gif'...
Packaging file 'STDFLogo.gif'...
Packaging file 'STDFAdmin2.gif'...
Packaging file 'Web.sitemap'...
Packaging file 'Spacer.gif'...
Packaging file 'GridHeaderBg.gif'...
Packaging file 'STDFReportPortal.dll'...
Packaging file 'PRONumberLookup.aspx'...
Packaging file 'delete_ico.gif'...
Packaging file 'STDFReportPortal.Master'...
Packaging file 'GreenBg1x1.gif'...
Packaging file 'GreenBorderBg.gif'...
Packaging file 'EFSetup.aspx'...
Packaging file 'TopBannerTitle.gif'...
Packaging file 'user_ico.gif'...
Packaging file 'UnbilledMissingDocs.aspx'...
Packaging file 'stdfStyle.css'...
Packaging file 'edit_ico.gif'...
Packaging file 'Default.aspx'...
Packaging file 'plus_ico.gif'...
Packaging file 'cancel_ico.gif'...
Packaging file 'stdfSkins.skin'...
Packaging file 'checkmark_red_ico.gif'...
Packaging file 'Web.config'...
Packaging file 'OrangeBg1x1.gif'...
========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========

cheong,

That's just the problem.  I'm not seeing any reason for the failed build, just that one failed to build.

[C]

I'm looking for any help I can get here.  I made a very simple web project.  It has four pages.  I then added a web setup project to my solution and added the primary output and content.

When I right click on the setup project and say build the main project builds but the setup project fails.  As far as I can tell, it just says 1 built and 1 failed.  I cannot even find a reason WHY it failed.

HINTS?!  Anybody know where I can even look to get more info about what failed?

Thank you - oh masters of web setup projects.

Would you care to comment more or explain bit more your last sentence, especially the part about ambiguity?  I'm not sure I followed that as well as I should have.

I totally followed the part about leads/seniors basically being the people that have stuck it out, or survived long enough to work on all the projects in a smallish shop.  But I didn't understand that last point you were trying to get at.

figuerres wrote:


if you need to have say 3 or more servers all be "Active - Active" and share the same data store you are looking at some kind of extenral disk system possibly a SAN and that costs $$$ to build and maintain.
then you have to have the servers all share access to that data store and not corrupt the data.
I think this can be done, is done for a few systems but in most cases it's overkill.

Hey, shared disk, good idea.  I'm gonna have to dig up some info on that.  That sounds like not a bad idea.  I know of several other applications that cluster in this manner.

figuerres wrote:


for example If I had to handle a high TP rate I might look at a way to deploy several servrs to handle that transaction load and then dump the data into the main server.

The concept of splitting the ordering or the high volume processing tables away into another instance is not a bad way either.  I noticed a somewhat similar approach in an application a couple years ago.  That takes some planning.  But I guess all of this would.

figuerres wrote:


something like that might get all the perf you need but with much less expensive hardware and software setup.

I think this is an excellent point and a good reminder to be cost aware.

figuerres wrote:

also -- MORE RAM !
SQL loves ram, eats it for breakast, lunch and dinner!
if you can have as much ram as the size of the database then go for it!

Uh...ya.  This is the one I'm not doing right now.  Need to get on that.

figuerres,

The setup you describe is probably the one I'm most familiar with...not trying to say I'm an expert or anything it is just the only thing in this thread so far I have experience with.  So, I guess one thing I'm wonders is when you talk about moving from a few thousand orders an hour to several hundred thousand transactions an hour or a minute are we expecting a single server to scale vertically?  Is that the only option on the SQL Server platform? 

What I'm getting at is this:  I'm not sure what I'm asking is realistic, just more like is it possible and where could I find info about it.

Currently at my job we have the scenario you discuss.  64 bit servers, 8 gigs RAM, quad processor.  One primary box, one failover.  An active/passive scenario.  Both are 2005 SQL Enterprise.

I agree with you on everything you've stated, but what about WHEN/IF you get to the point that machine cannot handle it?  At lesat not handle it as promptly as someone asks you to make it handle it.