“/”应用程序中的服务器错误。

The context cannot be used while the model is being created. This exception may be thrown if the context is used inside the OnModelCreating method or if the same context instance is accessed by multiple threads concurrently. Note that instance members of DbContext and related classes are not guaranteed to be thread safe.

说明: 执行当前 Web 请求期间,出现未经处理的异常。请检查堆栈跟踪信息,以了解有关该错误以及代码中导致错误的出处的详细信息。

异常详细信息: System.InvalidOperationException: The context cannot be used while the model is being created. This exception may be thrown if the context is used inside the OnModelCreating method or if the same context instance is accessed by multiple threads concurrently. Note that instance members of DbContext and related classes are not guaranteed to be thread safe.

源错误:


行 1:  @{PreviousNext.Get(Data);}
行 2:  <div class="view-page view-page2">
行 3:  @if (Data.previnfo != null)

源文件: d:\webhosting\clients\4d584dba-517f-41b6-89b9-463b0b1aea0e\wwwroot\Data\szhtf\template\en\程序代码\部件\_PreviousNext2.cshtml    行: 1

堆栈跟踪:


[InvalidOperationException: The context cannot be used while the model is being created. This exception may be thrown if the context is used inside the OnModelCreating method or if the same context instance is accessed by multiple threads concurrently. Note that instance members of DbContext and related classes are not guaranteed to be thread safe.]
   System.Data.Entity.Internal.LazyInternalContext.InitializeContext() +863
   System.Data.Entity.Internal.InternalContext.Initialize() +20
   System.Data.Entity.Internal.InternalContext.GetEntitySetAndBaseTypeForType(Type entityType) +16
   System.Data.Entity.Internal.Linq.InternalSet`1.Initialize() +53
   System.Data.Entity.Internal.Linq.InternalSet`1.AsNoTracking() +18
   System.Data.Entity.Infrastructure.DbQuery`1.AsNoTracking() +46
   QibuCMS.PreviousNext.Get(ViewModel model) +160
   ASP._Page_Data_szhtf_template_en_程序代码_部件__PreviousNext2_cshtml.Execute() in d:\webhosting\clients\4d584dba-517f-41b6-89b9-463b0b1aea0e\wwwroot\Data\szhtf\template\en\程序代码\部件\_PreviousNext2.cshtml:1
   System.Web.WebPages.WebPageBase.ExecutePageHierarchy() +197
   System.Web.Mvc.WebViewPage.ExecutePageHierarchy() +105
   System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage) +90
   System.Web.WebPages.<>c__DisplayClass40_0.<RenderPageCore>b__0(TextWriter writer) +232
   System.Web.WebPages.HelperResult.WriteTo(TextWriter writer) +10
   System.Web.WebPages.WebPageBase.Write(HelperResult result) +80
   ASP._Page_Data_szhtf_template_en_程序代码_new_cshtml.Execute() in d:\webhosting\clients\4d584dba-517f-41b6-89b9-463b0b1aea0e\wwwroot\Data\szhtf\template\en\程序代码\new.cshtml:23
   System.Web.WebPages.WebPageBase.ExecutePageHierarchy() +197
   System.Web.Mvc.WebViewPage.ExecutePageHierarchy() +105
   System.Web.WebPages.StartPage.RunPage() +17
   System.Web.WebPages.StartPage.ExecutePageHierarchy() +73
   System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage) +78
   System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance) +256
   System.Web.Mvc.BuildManagerCompiledView.Render(ViewContext viewContext, TextWriter writer) +107
   System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context) +291
   System.Web.Mvc.ControllerActionInvoker.InvokeActionResult(ControllerContext controllerContext, ActionResult actionResult) +13
   System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult) +56
   System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult) +420
   System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult) +420
   System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult) +52
   System.Web.Mvc.Async.<>c__DisplayClass3_6.<BeginInvokeAction>b__3() +198
   System.Web.Mvc.Async.<>c__DisplayClass3_1.<BeginInvokeAction>b__5(IAsyncResult asyncResult) +100
   System.Web.Mvc.Async.WrappedAsyncResult`1.CallEndDelegate(IAsyncResult asyncResult) +10
   System.Web.Mvc.Async.WrappedAsyncResultBase`1.End() +49
   System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +27
   System.Web.Mvc.<>c.<BeginExecuteCore>b__152_1(IAsyncResult asyncResult, ExecuteCoreState innerState) +11
   System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +29
   System.Web.Mvc.Async.WrappedAsyncResultBase`1.End() +49
   System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +45
   System.Web.Mvc.<>c.<BeginExecute>b__151_2(IAsyncResult asyncResult, Controller controller) +13
   System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +22
   System.Web.Mvc.Async.WrappedAsyncResultBase`1.End() +49
   System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +26
   System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +10
   System.Web.Mvc.<>c.<BeginProcessRequest>b__20_1(IAsyncResult asyncResult, ProcessRequestState innerState) +28
   System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +29
   System.Web.Mvc.Async.WrappedAsyncResultBase`1.End() +49
   System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +28
   System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +9
   System.Web.CallHandlerExecutionStep.InvokeEndHandler(IAsyncResult ar) +152
   System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +125


版本信息: Microsoft .NET Framework 版本:4.0.30319; ASP.NET 版本:4.7.3429.0
家居装饰软硬结合 演绎出东方文化的缥缈与神秘-五星级酒店布草_客房餐饮布草_酒店台布_汇庭芳纺织-官网
News
Current locationHome>News>Industry News
家居装饰软硬结合 演绎出东方文化的缥缈与神秘

Upload time:2014-07-15|Author:admin

1563160932(1).jpg
伴随人们生活水平的提高,单纯的功能性空间已满足不了人们的精神追求,人们用“家居配饰” “软装饰”等词汇去努力描述家居空间所要营造出的氛围的重要性。家居软装饰就是通过完美设计手法将所要表达的空间意境呈现在整个空间内,使得整个空间满足人们的物质追求和精神追求。

“软装饰”和“硬装饰”是相互渗透的。在现代的装饰设计中,木石、水泥、瓷砖、玻璃等建筑材料和丝麻等纺织品都是相互交叉,彼此渗透,有时也是可以相互替代的。比如:对于房顶的装饰,人们往往拘泥于木制、石膏这些硬装饰材料。

实际上,用丝织品在室内的上部空间做一个拉膜,拉出一个优美的弧线,不仅会起到异化空间的效果,还会有些许的神秘感渗出,成为整个房间的亮点。这种概念化空间的“软装饰”源于我国古代宫闱中层层叠叠的纱幔,它充分表现出东方文化的缥缈与神秘。目前“软装饰”在家装中的比例并不高,平均只占到5%,但未来的10年之中它将占到20%甚至更多。

据业内人士分析,装饰布料的发展趋势之一就是人们将广泛选用布坯原料。从常见的涤纶、丙纶、锦纶、棉等原料到新型的复合纤维、异型纤维、闪光纤维的应用,再经过特殊的加工处理,就能够创造出不同的效果。图案和色彩是软装的灵魂所在,两者的无穷变化就能演绎出迥异的风格。

欧式古典主义用精美的罗马帘、华贵的床罩与纯毛地毯以及造型典雅的灯具和高贵的油画来达到雍容华贵的装饰效果。需要注意的是应避免过于奢华的装饰破坏了自然的家居气氛。

中式古典主义以清新淡雅为主,碎花的窗帘、通透的帷幔、书香浓郁的卷轴字画以及水仙、文竹等绿色植物已成为中式古典主义不可或缺的软装饰。

现代主义这种风格强调功能至上,以实用、舒适为原则,没有标志性的软装饰,以兼收并蓄为其特色。它的优点是搭配灵活,容易产生变化,但弄不好也容易失之杂乱,难以形成统一风格。

深圳市汇庭芳纺织品有限公司(www.szhtf.com)主要面向酒店生产、销售专用宾馆布草。产品包括高端酒店布草,酒店毛巾,酒店床上用品,客房布草,餐饮布草,酒店布草等。欢迎大家前来咨询和选购!

—— Contact Us ——
Add:7A, Building 2, Anle Industrial Park, Beiba Road, Hezhou Village, Xixiang Town, Bao'an District, Shenzhen, China
Mr. Liu:13502846712  
Miss Yu:13714295560  
Fax:0755-29980629  
E-mail:szhtf@126.com  

WeChat

CopyRight © 2019 Shenzhen Huitingfang Textile Co., Ltd. All Right Reserved. 粤ICP备14001694号